For sure. I am using a repo that has React components as a dependency for another React project (let's call this the parent_repo ), both of which use ES6 and 7 syntax. So I would like to use webpack with parent_repo and tell the babel loader to compile my child_repo , instead of the usual ignoring of node_modules. I'm trying to be able to develop fast locally by being able to npm link the child_repo and have webpack recompile both the parent and child, seeing changes with HMR. Perhaps even my setup is blasphemous. When I use npm-link though, a lot of the resolving goes haywire. I have a number of plugins for the parent_repo and they cannot be found when the child_repo is compiling. Similar problems for loaders.

What is the best way to specify that a loader should compile a dependency from npm and have that working with npm link? I see that there are some issues with path.join and path.resolve with the resolve and resolveLoader settings.