bbs
Reputation: 2022
Webpack module resolving only working for some directories
When trying to port a project from webpack-isomorphic-tools to universal-webpack I ran into a strange issue resolving module dependencies.
It seems modules in node_modules, src/js and src/js/constants/* get resolved. But I get the infamous "cannot resolve module" error on modules that are in any other directories at the same level as constants. I can't find anything that changes how webpack should treat src/js/constants`
The project's webpack config and part of the tree of src/js:
https://gist.github.com/bbss/ffebfaa6bbd9fa1d8e6f6c6842e4add5
I'm not sure how to approach debugging this so any pointers would be appreciated.
Upvotes: 2
Views: 67
Answers (0)
Related Questions
- Webpack can't resolve asset/resource?
- Webpack dist folder not served
- Webpack. Resolve several paths with import
- Webpack resolve compiles, but errors in the browser
- configure webpack to use absolute path instead of relative path
- Webpack cannot resolve relative path
- Webpack fails to find module dirs
- webpack cannot resolve folders in reactjs app on deployment
- Resolving relative paths in React with Webpack not working
- Webpack not serving files in subdirectories?