MyComponent/index.js? or ALWAYS have file name reflect default export?

Regarding this issue: https://github.com/airbnb/javascript/issues/949

I find it difficult to work in RubyMine/Webstorm with tons of files named index.js:

• Have to remember to hit a / after typing the name and autocomplete is not great
• Search results harder to read.

I’d like to suggest the following convention:

1. Create the file as components/MyComponent/MyComponent.js;
2. Create an “index” file in that directory with one line: export { default } from ./MyComponent.js`
3. Do the import as: import MyComponent from 'components/MyComponent'; (using the default for the directory.

I believe this may give the best of both worlds in that

1. The files are named per the default export.
2. Easier file navigation in most editors.
3. Avoid having multiple editor tabs open that say index.js.
4. Still have the concise import statement for the main file in a directory.

The cost is only to add the index.js file in each directory with a default component.

[radixhound]

FWIW I removed my comments because I had the context of the issue wrong methinks.

[prigara]

For those who will bump into this issue in the future: this pattern works fine in IntelliJ-based IDEs. import boo from 'foo' will resolve into foo/index.js if there’s such file.