Can I custom modulesDirectories ?

[suhaotian]

├── src
│   ├── App.js
│   ├── assets
│   │   └── logo.png
│   ├── components
│   │   ├── Counter.js
│   │   ├── Hello.js
│   │   └── Todo.js
│   ├── main.js
│   └── router
│   └── index.js

I just want to write like this to import componets in App.js:
(It's good for deep nested folder to import components.)

import Todo from 'components/Todo'

not

import Todo from './components/Todo'

I don't want to run eject, thank you !

[suhaotian]

#1136

[gaearon]

See my reply in #1607 (comment).
Please search past issues before creating a new one.
Thank you!

[JustinTRoss]

The two issues mentioned above cover resolve.root (absolute path) configuration rather than resolve.modulesDirectories (hierarchal modules folders).

Any suggestions on how to achieve this without ejecting or having node_modules folders all over the place?

[gaearon]

If you want arbitrary folders to have the same behavior as node_modules, that's not supported. This is just not how Node resolution algorithm works, and we do our best to stay compatible with it. Please symlink any custom folders to node_modules if it is important to you.

[JustinTRoss]

10-4. Thanks.

[Altiano]

@gaearon How about add another environment variable like customResolveModules or something like that.
And in paths.js or webpack.[dev|prod].js the variable should be injected.

[gaearon]

I don’t think we’ll do that. We don’t want to significantly deviate from Node resolution algorithm. Instead we’d want to push the ecosystem towards solutions that work well within it.

[Altiano]

Yeah there are many hacky ways for typing less when requiring local module, guess we need to stick with those. But I'm wondering what is your recommended solution to require component from deeply nested module?

*) Maybe the solution could be places in User Guide section, so there are no more similar issue

[gaearon]

You can put NODE_PATH=src in your .env file.

[Altiano]

@gaearon cool!