-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase verbosity for "Module not found" errors, to prevent case sensitiveness problems #1278
Comments
Can you raise an issue with your suggestions in https://github.com/Urthen/case-sensitive-paths-webpack-plugin? It is not exactly clear to me what is actionable here on our side. |
@caesarsol So did you solve your problem? I seemed to always get this message, I don't know how to solve it. I have to comment out the |
Hey @edmundtfy, The problem was easily solved by changing the filenames in the git repo, to their right casing. Going to open the issue on the plugin today! |
@caesarsol
|
Is it working after you restart the webpack server and/or reinstall all npm packages? You may be running in something like Urthen/case-sensitive-paths-webpack-plugin#17? |
@caesarsol it is not working after restart, but is good after reinstall all npm packages... I guess more related to that issues you link to |
Thats surprising, I don't know if it has anything to do with this at this point. I'm sorry! |
Closing as stale. |
As discussed with @gaearon in #1260
My problem had to do with:
The CI builds failed, the local was OK, and I lost hours because I had no access to CI machine and I was misleaded by the undescriptive error message.
My proposal is to leverage something similar to the CaseSensitiveWebpackPlugin to give a more verbose error message, for example a directory listing or the searched paths.
The text was updated successfully, but these errors were encountered: