ERROR in Entry module not found: Error: Cannot resolve 'file' or 'directory'
See original GitHub issueWhen using 1.4.0 I get the error above, <1.4.0 works great. complaint is ./spec/index.js
, I assume files
is the culprit, not preprocessors
:
files: [
'./spec/index.js'
],
or
preprocessors: {
'./spec/index.js': ['webpack']
},
Coincidentally, I see the new webpack-karma reporter is spec
, however I can’t imagine that causing a clash.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:2
- Comments:33 (4 by maintainers)
Top Results From Across the Web
ERROR in Entry module not found: Error: Cannot resolve 'file ...
Hi everybody. I'm simply trying to use webpack but i can't solve this error. This is my webpack.config.js : module.exports = { entry:...
Read more >72 - Stack Overflow
So if you get this error you need to really look at your entry path and make sure it is right based on...
Read more >踩坑场景 - 掘金
ERROR in Entry module not found: Error: Can't resolve './src' in XXX的一个解决方案. 踩坑场景. 今天在学习Vue 的webpack 时(使用配置文件 ...
Read more >webpack@4 default value for entry - appsloveworld
[Solved]-Entry module not found: Error: Can't resolve './src'-Reactjs ... Moreover, move your webpack config file to the root folder. entry: ...
Read more >webpack/webpack - Gitter
ERROR in Entry module not found: Error: Can't resolve './src' in '/Users/me/company/assets' error Command failed with exit code 2. const buildConfigs = [{...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Keats post on Stackoverflow has a good solution.
set the extensions property on Webpack resolve configuration like this:
webpackConfig.resolve.extensions = [‘’, ‘.js’, ‘.coffee’] //ts, or anything else
That solved it for me.
I think Webpack’s error are really unfriendly… I tried for half an hour but failed to found out what’s wrong when it gives this error.