blocks|key|4514808|text|我不认为这是可能的，但afaik模块名称的解析取决于模块加载器，所以可能有一个加载器实现支持这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4514809|在此之前，您可以在lib/things/index.js中使用一个只包含以下内容的中间“模块文件”|offset|length|style|CODE|4514810|export+*+from+'ThingA';
export+*+from+'ThingB';
export+*+from+'ThingC';|code-block|syntax|javascript|4514811|它可以让你做|4514812|import+{ThingA,+ThingB,+ThingC}+from+'lib/things';|4514813|entityMap^0|0|9|J|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I don't think this is possible, but afaik the resolution of module names is up to module loaders so there might a loader implementation that does support this.

Until then, you could use an intermediate "module file" at <code>lib/things/index.js</code> that just contains

<pre><code>export * from 'ThingA';
export * from 'ThingB';
export * from 'ThingC';
</code></pre>

and it would allow you to do

<pre><code>import {ThingA, ThingB, ThingC} from 'lib/things';
</code></pre>

blocks|key|7303|text|这只是答案中已经提供的主题的一个变体，但是这个怎么样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7304|在Thing中，|offset|length|style|CODE|7305|export+default+function+ThingA+()+{}|code-block|syntax|javascript|7306|在things/index.js中，|7307|export+{default+as+ThingA}+from+'./ThingA'
export+{default+as+ThingB}+from+'./ThingB'
export+{default+as+ThingC}+from+'./ThingC'|7308|然后在别处消费所有的东西，|7309|import+*+as+things+from+'./things'
things.ThingA()|7310|或者只消耗一些东西，|7311|import+{ThingA,ThingB}+from+'./things'|7312|entityMap^0|0|1|5|0|0|1|F|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|J|7|1C|8|@]|9|@]|A|$K|L]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

Just a variation on the theme already provided in the answer, but how about this:

In a <code>Thing</code>,

<pre><code>export default function ThingA () {}
</code></pre>

In <code>things/index.js</code>,

<pre><code>export {default as ThingA} from './ThingA'
export {default as ThingB} from './ThingB'
export {default as ThingC} from './ThingC'
</code></pre>

Then to consume all the things elsewhere,

<pre><code>import * as things from './things'
things.ThingA()
</code></pre>

Or to consume just some of things,

<pre><code>import {ThingA,ThingB} from './things'
</code></pre>

blocks|key|4514870|text|如果您不导出A、B、C中的默认值，而只是导出{}，则可以这样做|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4514871|//+things/A.js
export+function+A()+{}

//+things/B.js
export+function+B()+{}

//+things/C.js
export+function+C()+{}

//+foo.js
import+*+as+Foo+from+./thing
Foo.A()
Foo.B()
Foo.C()|code-block|syntax|javascript|4514872|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

if you don't export default in A, B, C but just export {} then it's possible to do so

<pre><code>// things/A.js
export function A() {}

// things/B.js
export function B() {}

// things/C.js
export function C() {}

// foo.js
import * as Foo from ./thing
Foo.A()
Foo.B()
Foo.C()
</code></pre>

blocks|key|7382|text|我已经使用它们几次了(特别是为了构建大量的对象，将数据分散到许多文件中(例如AST节点))，为了构建它们，我制作了一个小脚本(我刚刚将其添加到npm中，以便其他所有人都可以使用它)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7383|用法(当前您需要使用babel才能使用导出文件)：|7384|$+npm+install+-g+folder-module
$+folder-module+my-cool-module/|code-block|syntax|javascript|7385|生成包含以下内容的文件：|7386|export+{default+as+foo}+from+"./module/foo.js"
export+{default+as+default}+from+"./module/default.js"
export+{default+as+bar}+from+"./module/bar.js"
...etc|7387|然后，您可以只使用该文件：|7388|import+*+as+myCoolModule+from+"my-cool-module.js"
myCoolModule.foo()|7389|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I've used them a few times (in particular for building massive objects splitting the data over many files (e.g. AST nodes)), in order to build them I made a tiny script (which I've just added to npm so everyone else can use it).

Usage (currently you'll need to use babel to use the export file):

<pre><code>$ npm install -g folder-module
$ folder-module my-cool-module/
</code></pre>

Generates a file containing:

<pre><code>export {default as foo} from "./module/foo.js"
export {default as default} from "./module/default.js"
export {default as bar} from "./module/bar.js"
...etc
</code></pre>

Then you can just consume the file:

<pre><code>import * as myCoolModule from "my-cool-module.js"
myCoolModule.foo()
</code></pre>

blocks|key|7410|text|这只是@Bergi答案的另一种方式|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7411|//+lib/things/index.js
import+ThingA+from+'./ThingA';
import+ThingB+from+'./ThingB';
import+ThingC+from+'./ThingC';

export+default+{
+ThingA,
+ThingB,
+ThingC
}|code-block|syntax|javascript|7412|使用|7413|import+{ThingA,+ThingB,+ThingC}+from+'./lib/things';|7414|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Just an other approach to @Bergi's answer

<pre><code>// lib/things/index.js
import ThingA from './ThingA';
import ThingB from './ThingB';
import ThingC from './ThingC';

export default {
 ThingA,
 ThingB,
 ThingC
}
</code></pre>

Uses

<pre><code>import {ThingA, ThingB, ThingC} from './lib/things';
</code></pre>

blocks|key|4514970|text|这并不完全是你想要的，但是使用这个方法，我可以在我的其他文件中迭代componentsList，并使用像componentsList.map(...)这样的函数，我发现它非常有用！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4514971|import+StepOne+from+'./StepOne';
import+StepTwo+from+'./StepTwo';
import+StepThree+from+'./StepThree';
import+StepFour+from+'./StepFour';
import+StepFive+from+'./StepFive';
import+StepSix+from+'./StepSix';
import+StepSeven+from+'./StepSeven';
import+StepEight+from+'./StepEight';

const+componentsList=+()+=>+[
++{+component:+StepOne(),+key:+'step1'+},
++{+component:+StepTwo(),+key:+'step2'+},
++{+component:+StepThree(),+key:+'step3'+},
++{+component:+StepFour(),+key:+'step4'+},
++{+component:+StepFive(),+key:+'step5'+},
++{+component:+StepSix(),+key:+'step6'+},
++{+component:+StepSeven(),+key:+'step7'+},
++{+component:+StepEight(),+key:+'step8'+}
];

export+default+componentsList;|code-block|syntax|javascript|4514972|entityMap^0|X|E|1G|N|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

This is not exactly what you asked for but, with this method I can Iterate throught <code>componentsList</code> in my other files and use function such as <code>componentsList.map(...)</code> which I find pretty usefull !

<pre><code>import StepOne from './StepOne';
import StepTwo from './StepTwo';
import StepThree from './StepThree';
import StepFour from './StepFour';
import StepFive from './StepFive';
import StepSix from './StepSix';
import StepSeven from './StepSeven';
import StepEight from './StepEight';

const componentsList= () =&gt; [
 { component: StepOne(), key: 'step1' },
 { component: StepTwo(), key: 'step2' },
 { component: StepThree(), key: 'step3' },
 { component: StepFour(), key: 'step4' },
 { component: StepFive(), key: 'step5' },
 { component: StepSix(), key: 'step6' },
 { component: StepSeven(), key: 'step7' },
 { component: StepEight(), key: 'step8' }
];

export default componentsList;
</code></pre>

blocks|key|4515018|text|很棒的恶作剧！这比它需要的更难。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4515019|导出一个平面默认值|4515020|这是使用spread的绝佳机会(+{+...Matters,+...Contacts+}中的...如下所示：|offset|length|style|CODE|4515021|//+imports/collections/Matters.js
export+default+{+++++++++++//+default+export
++hello:+'World',
++something:+'important',
};|code-block|syntax|javascript|4515022|//+imports/collections/Contacts.js
export+default+{+++++++++++//+default+export
++hello:+'Moon',
++email:+'hello@example.com',
};|4515023|//+imports/collections/index.js
import+Matters+from+'./Matters';++++++//+import+default+export+as+var+'Matters'
import+Contacts+from+'./Contacts';

export+default+{++//+default+export
++...Matters,+++++//+spread+Matters,+overwriting+previous+properties
++...Contacts,++++//+spread+Contacts,+overwriting+previosu+properties
};|4515024|//+imports/test.js
import+collections+from+'./collections';++//+import+default+export+as+'collections'

console.log(collections);|4515025|然后，转到run+babel+compiled+code+from+the+command+line+(从项目根目录/)：|4515026|$+npm+install+--save-dev+@babel/core+@babel/cli+@babel/preset-env+@babel/node+
(trimmed)

$+npx+babel-node+--presets+@babel/preset-env+imports/test.js+
{+hello:+'Moon',
++something:+'important',
++email:+'hello@example.com'+}|4515027|导出一个类似树的默认设置|4515028|如果您不想覆盖属性，请更改：|4515029|//+imports/collections/index.js
import+Matters+from+'./Matters';+++++//+import+default+as+'Matters'
import+Contacts+from+'./Contacts';

export+default+{+++//+export+default
++Matters,
++Contacts,
};|4515030|输出结果为：|4515031|$+npx+babel-node+--presets+@babel/preset-env+imports/test.js
{+Matters:+{+hello:+'World',+something:+'important'+},
++Contacts:+{+hello:+'Moon',+email:+'hello@example.com'+}+}|4515032|导出多个命名导出(有/无默认值)|4515033|如果您专注于DRY，那么导入的语法也会发生变化：|4515034|//+imports/collections/index.js

//+export+default+as+named+export+'Matters'
export+{+default+as+Matters+}+from+'./Matters';++
export+{+default+as+Contacts+}+from+'./Contacts';+|4515035|这将创建2个有/无缺省导出的命名导出。然后改变：|4515036|//+imports/test.js
import+{+Matters,+Contacts+}+from+'./collections';

console.log(Matters,+Contacts);|4515037|和输出：|4515038|$+npx+babel-node+--presets+@babel/preset-env+imports/test.js
{+hello:+'World',+something:+'important'+}+{+hello:+'Moon',+email:+'hello@example.com'+}|4515039|导入所有命名导出|4515040|//+imports/collections/index.js

//+export+default+as+named+export+'Matters'
export+{+default+as+Matters+}+from+'./Matters';
export+{+default+as+Contacts+}+from+'./Contacts';|4515041|//+imports/test.js

//+Import+all+named+exports+as+'collections'
import+*+as+collections+from+'./collections';

console.log(collections);++//+interesting+output
console.log(collections.Matters,+collections.Contacts);|4515042|请注意上一个示例中的destructuring+import+{+Matters,+Contacts+}+from+'./collections';。|4515043|$+npx+babel-node+--presets+@babel/preset-env+imports/test.js
{+Matters:+[Getter],+Contacts:+[Getter]+}
{+hello:+'World',+something:+'important'+}+{+hello:+'Moon',+email:+'hello@example.com'+}|4515044|在实践中|4515045|给定这些源文件：|4515046|/myLib/thingA.js
/myLib/thingB.js
/myLib/thingC.js|4515047|创建一个/myLib/index.js来捆绑所有文件与导入/导出的目的背道而驰。比起通过index.js“包装器文件”导入/导出，首先让所有东西都变得全局要容易得多。|4515048|如果你想要一个特定的文件，在你自己的项目中使用import+thingA+from+'./myLib/thingA';。|4515049|只有当您为npm或多年的多团队项目打包时，才能为模块创建一个带有导出的“包装器文件”。|4515050|走到这一步了？有关更多详细信息，请参阅docs。|4515051|另外，Stackoverflow终于支持三个作为代码栏标记。|4515052|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax|1|https://stackoverflow.com/questions/51530249/how-to-run-node-babel-script-directly-in-command-line/54755768#54755768|2|https://en.wikipedia.org/wiki/Don't_repeat_yourself|3|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment#Object_destructuring|4|https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export^0|0|0|H|R|1A|3|4|6|0|0|0|0|0|0|5|19|1|0|0|0|0|0|0|0|0|6|3|2|0|0|0|0|0|0|0|0|0|O|1E|A|D|3|0|0|0|0|0|4|F|0|N|10|0|0|J|4|4|0|0^^$0|@$1|2|3|4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2U|8|@$F|2V|G|2W|H|I]|$F|2X|G|2Y|H|I]]|9|@$F|2Z|G|30|1|31]]|A|$]]|$1|J|3|K|5|L|7|32|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|L|7|33|8|@]|9|@]|A|$M|N]]|$1|Q|3|R|5|L|7|34|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|L|7|35|8|@]|9|@]|A|$M|N]]|$1|U|3|V|5|6|7|36|8|@]|9|@$F|37|G|38|1|39]]|A|$]]|$1|W|3|X|5|L|7|3A|8|@]|9|@]|A|$M|N]]|$1|Y|3|Z|5|6|7|3B|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|3C|8|@]|9|@]|A|$]]|$1|12|3|13|5|L|7|3D|8|@]|9|@]|A|$M|N]]|$1|14|3|15|5|6|7|3E|8|@]|9|@]|A|$]]|$1|16|3|17|5|L|7|3F|8|@]|9|@]|A|$M|N]]|$1|18|3|19|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|3H|8|@]|9|@$F|3I|G|3J|1|3K]]|A|$]]|$1|1C|3|1D|5|L|7|3L|8|@]|9|@]|A|$M|N]]|$1|1E|3|1F|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|L|7|3N|8|@]|9|@]|A|$M|N]]|$1|1I|3|1J|5|6|7|3O|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|L|7|3P|8|@]|9|@]|A|$M|N]]|$1|1M|3|1N|5|6|7|3Q|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|L|7|3R|8|@]|9|@]|A|$M|N]]|$1|1Q|3|1R|5|L|7|3S|8|@]|9|@]|A|$M|N]]|$1|1S|3|1T|5|6|7|3T|8|@$F|3U|G|3V|H|I]]|9|@$F|3W|G|3X|1|3Y]]|A|$]]|$1|1U|3|1V|5|L|7|3Z|8|@]|9|@]|A|$M|N]]|$1|1W|3|1X|5|6|7|40|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|41|8|@]|9|@]|A|$]]|$1|20|3|21|5|L|7|42|8|@]|9|@]|A|$M|N]]|$1|22|3|23|5|6|7|43|8|@$F|44|G|45|H|I]]|9|@]|A|$]]|$1|24|3|25|5|6|7|46|8|@$F|47|G|48|H|I]]|9|@]|A|$]]|$1|26|3|27|5|6|7|49|8|@]|9|@]|A|$]]|$1|28|3|29|5|6|7|4A|8|@]|9|@$F|4B|G|4C|1|4D]]|A|$]]|$1|2A|3|2B|5|6|7|4E|8|@]|9|@]|A|$]]|$1|2C|3|-4|5|6|7|4F|8|@]|9|@]|A|$]]]|2D|$2E|$5|2F|2G|2H|A|$2I|2J]]|2K|$5|2F|2G|2H|A|$2I|2L]]|2M|$5|2F|2G|2H|A|$2I|2N]]|2O|$5|2F|2G|2H|A|$2I|2P]]|2Q|$5|2F|2G|2H|A|$2I|2R]]]]

Great gugly muglys! This was harder than it needed to be.

<h1>Export one flat default</h1>

This is a great opportunity to use <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax" rel="noreferrer">spread</a> (<code>...</code> in <code>{ ...Matters, ...Contacts }</code> below:

<pre><code>// imports/collections/Matters.js
export default { // default export
 hello: 'World',
 something: 'important',
};
</code></pre>

<pre><code>// imports/collections/Contacts.js
export default { // default export
 hello: 'Moon',
 email: 'hello@example.com',
};
</code></pre>

<pre><code>// imports/collections/index.js
import Matters from './Matters'; // import default export as var 'Matters'
import Contacts from './Contacts';

export default { // default export
 ...Matters, // spread Matters, overwriting previous properties
 ...Contacts, // spread Contacts, overwriting previosu properties
};

</code></pre>

<pre><code>// imports/test.js
import collections from './collections'; // import default export as 'collections'

console.log(collections);
</code></pre>

Then, to <a href="https://stackoverflow.com/questions/51530249/how-to-run-node-babel-script-directly-in-command-line/54755768#54755768">run babel compiled code from the command line</a> (from project root /):

<pre class="lang-sh prettyprint-override"><code>$ npm install --save-dev @babel/core @babel/cli @babel/preset-env @babel/node 
(trimmed)

$ npx babel-node --presets @babel/preset-env imports/test.js 
{ hello: 'Moon',
 something: 'important',
 email: 'hello@example.com' }
</code></pre>

<h1>Export one tree-like default</h1>

If you'd prefer to not overwrite properties, change:

<pre><code>// imports/collections/index.js
import Matters from './Matters'; // import default as 'Matters'
import Contacts from './Contacts';

export default { // export default
 Matters,
 Contacts,
};
</code></pre>

And the output will be:

<pre class="lang-sh prettyprint-override"><code>$ npx babel-node --presets @babel/preset-env imports/test.js
{ Matters: { hello: 'World', something: 'important' },
 Contacts: { hello: 'Moon', email: 'hello@example.com' } }
</code></pre>

<h1>Export multiple named exports w/ no default</h1>

If you're dedicated to <a href="https://en.wikipedia.org/wiki/Don&#39;t_repeat_yourself" rel="noreferrer">DRY</a>, the syntax on the imports changes as well:

<pre><code>// imports/collections/index.js

// export default as named export 'Matters'
export { default as Matters } from './Matters'; 
export { default as Contacts } from './Contacts'; 
</code></pre>

This creates 2 named exports w/ no default export. Then change:

<pre><code>// imports/test.js
import { Matters, Contacts } from './collections';

console.log(Matters, Contacts);
</code></pre>

And the output: 

<pre class="lang-sh prettyprint-override"><code>$ npx babel-node --presets @babel/preset-env imports/test.js
{ hello: 'World', something: 'important' } { hello: 'Moon', email: 'hello@example.com' }
</code></pre>

<h1>Import all named exports</h1>

<pre><code>// imports/collections/index.js

// export default as named export 'Matters'
export { default as Matters } from './Matters';
export { default as Contacts } from './Contacts';
</code></pre>

<pre><code>// imports/test.js

// Import all named exports as 'collections'
import * as collections from './collections';

console.log(collections); // interesting output
console.log(collections.Matters, collections.Contacts);
</code></pre>

Notice the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment#Object_destructuring" rel="noreferrer">destructuring</a> <code>import { Matters, Contacts } from './collections';</code> in the previous example.

<pre class="lang-sh prettyprint-override"><code>$ npx babel-node --presets @babel/preset-env imports/test.js
{ Matters: [Getter], Contacts: [Getter] }
{ hello: 'World', something: 'important' } { hello: 'Moon', email: 'hello@example.com' }
</code></pre>

<h1>In practice</h1>

Given these source files:

<pre><code>/myLib/thingA.js
/myLib/thingB.js
/myLib/thingC.js
</code></pre>

Creating a <code>/myLib/index.js</code> to bundle up all the files defeats the purpose of import/export. It would be easier to make everything global in the first place, than to make everything global via import/export via index.js "wrapper files".

If you want a particular file, <code>import thingA from './myLib/thingA';</code> in your own projects.

Creating a "wrapper file" with exports for the module only makes sense if you're packaging for npm or on a multi-year multi-team project.

Made it this far? See the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export" rel="noreferrer">docs</a> for more details.

Also, yay for Stackoverflow finally supporting three `s as code fence markup.

blocks|key|4515067|text|现在可以使用async+import()：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4515068|import+fs+=+require('fs');|code-block|syntax|javascript|4515069|然后：|4515070|fs.readdir('./someDir',+(err,+files)+=>+{
+files.forEach(file+=>+{
++const+module+=+import('./'+%2B+file).then(m+=>
++++m.callSomeMethod();
++);
++//+or+const+module+=+await+import('file')
++});
});|4515071|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You now can use async import():
<pre><code>import fs = require('fs');
</code></pre>
and then:
<pre><code>fs.readdir('./someDir', (err, files) =&gt; {
 files.forEach(file =&gt; {
 const module = import('./' + file).then(m =&gt;
 m.callSomeMethod();
 );
 // or const module = await import('file')
 });
});
</code></pre>

blocks|key|7530|text|您也可以使用require：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7531|const+moduleHolder+=+[]

function+loadModules(path)+{
++let+stat+=+fs.lstatSync(path)
++if+(stat.isDirectory())+{
++++//+we+have+a+directory:+do+a+tree+walk
++++const+files+=+fs.readdirSync(path)
++++let+f,
++++++l+=+files.length
++++for+(var+i+=+0;+i+<+l;+i%2B%2B)+{
++++++f+=+pathModule.join(path,+files[i])
++++++loadModules(f)
++++}
++}+else+{
++++//+we+have+a+file:+load+it
++++var+controller+=+require(path)
++++moduleHolder.push(controller)
++}
}|code-block|syntax|javascript|7532|然后将您的moduleHolder与动态加载的控制器一起使用：|7533|++loadModules(DIR)+
++for+(const+controller+of+moduleHolder)+{
++++controller(app,+db)
++}|7534|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can use require as well:

<pre><code>const moduleHolder = []

function loadModules(path) {
 let stat = fs.lstatSync(path)
 if (stat.isDirectory()) {
 // we have a directory: do a tree walk
 const files = fs.readdirSync(path)
 let f,
 l = files.length
 for (var i = 0; i &lt; l; i++) {
 f = pathModule.join(path, files[i])
 loadModules(f)
 }
 } else {
 // we have a file: load it
 var controller = require(path)
 moduleHolder.push(controller)
 }
}
</code></pre>

Then use your moduleHolder with dynamically loaded controllers:

<pre><code> loadModules(DIR) 
 for (const controller of moduleHolder) {
 controller(app, db)
 }
</code></pre>

blocks|key|4515123|text|我借鉴了用户atilkan的方法，并对其进行了一些修改：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4515124|对于Typescript用户；|4515125|require.context('@/folder/with/modules',+false,+/\.ts$/).keys().forEach((fileName+=>+{
++++import('@/folder/with/modules'+%2B+fileName).then((mod)+=>+{
++++++++++++(window+as+any)[fileName]+=+mod[fileName];
++++++++++++const+module+=+new+(window+as+any)[fileName]();

++++++++++++//+use+module
});

}));|code-block|syntax|javascript|4515126|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was able to take from user atilkan's approach and modify it a bit:

For Typescript users;

<pre><code>require.context('@/folder/with/modules', false, /\.ts$/).keys().forEach((fileName =&gt; {
 import('@/folder/with/modules' + fileName).then((mod) =&gt; {
 (window as any)[fileName] = mod[fileName];
 const module = new (window as any)[fileName]();

 // use module
});

}));
</code></pre>

With ES6, I can import several exports from a file like this:

<pre><code>import {ThingA, ThingB, ThingC} from 'lib/things';
</code></pre>

However, I like the organization of having one module per file. I end up with imports like this:

<pre><code>import ThingA from 'lib/things/ThingA';
import ThingB from 'lib/things/ThingB';
import ThingC from 'lib/things/ThingC';
</code></pre>

I would love to be able to do this:

<pre><code>import {ThingA, ThingB, ThingC} from 'lib/things/*';
</code></pre>

or something similar, with the understood convention that each file contains one default export, and each module is named the same as its file.

Is this possible?

Is it possible to import modules from all files in a directory, using a wildcard?

使用ES6，我可以从一个文件中导入多个导出，如下所示：import {ThingA, ThingB, ThingC} from 'lib/things';但是，我喜欢每个文件有一个模块的组织。我最终得到了这样的导入：import ThingA from 'lib/things/ThingA';import ThingB...

问是否可以使用通配符从目录中的所有文件导入模块？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以使用通配符从目录中的所有文件导入模块？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以使用通配符从目录中的所有文件导入模块？
EN