Tommy

@ViktorAksionov Out of curiosity, would you have a small repro project with the issue? This is the first time I hear that the root configuration is making a deep resolution...

Hmm.. Afaik, the `json` extension is not mandatory in node either so your path `'../fixtures/foo'` should definitely work. Would you have a test repo by any chance?

> I don't understand why you are stripping the extensions at all, shouldn't you just be using the file that was resolved? Because the extensions are not needed for node...

@wardpeet There wasn't any real reason to be honest. My first implementation didn't use any custom extension (that was done later on in the development process), so it wasn't needed...

Why would it need to be `/index`? `index.js` is the default file loaded in a directory

@fatfisz any idea? Would definitely like to fix it before the next release. I'll add that on my todo to check the given example and try to find out the...

The plugin doesn't currently support the custom loaders from webpack in the paths. I'd suggest you to put the info in your webpack config and then use a normal path...

@machineghost Are you saying `dynamic-import-webpack` would replace the import statement in `b.js` with `require('~/a')`? Because if this is the case, `module-resolve` also supports reading CJS. Not sure why `module-resolver` wouldn't...

I don't see a direct issue with `dynamic-import-webpack` (see #278). And we support transforming path in `require` as well. But it seems the new require statement is not even read...

This is weird that the error mentions `module-alias` when your babelrc file says `module-resolver`. Are you sure you gave us the content from `/Users/mymac/Documents/Projects/disi/.babelrc`?