Module Not Found
See original GitHub issueI’am using webpack and I got this error
ERROR in ../~/angular-spinner/angular-spinner.js Module not found: Error: Cannot resolve module 'spin' in /home/gabriel/Development/garavano/node_modules/angular-spinner @ ../~/angular-spinner/angular-spinner.js 132:2-38
I solved it by changing ‘spin’ to ‘spin.js’ in line 132
define(['angular', 'spin.js'], factory);
Is this an issue for anyone else?
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
module-not-found - Next.js
The module you're trying to import is not installed in your dependencies · The module you're trying to import is in a different...
Read more >ModuleNotFoundError: no module named Python Error [Fixed]
How to fix the ModuleNotFoundError in Python · 1. Make sure imported modules are installed · 2. Make sure modules are spelled correctly...
Read more >javascript - Module not found can't resolve - Stack Overflow
app/index.js Module not found: Error: Can't resolve './app/test.js'. I've tried changing the file path to a relative one with no luck and ...
Read more >Have a JavaScript Module Not Found Error ... - Airbrake Blog
Most likely, the reason you're seeing a “module not found” error message within your JavaScript code will be something simple, like putting an ......
Read more >How to fix 'Module not found: Can't resolve 'http' in ... - YouTube
Basically, just change 'react-scripts' to 4.0.2 in your package.json and run `npm install` again :D Follow me on Twitter: ...
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 FreeTop 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
Top GitHub Comments
Here’s a solution for webpack that doesn’t require modifying the package:
then in
webpack.config.js
:Hi community folks,
We’ve decided to refactor the whole base code because of the many requests of webpack and amd compatibility issues, and we’re using already webpack in master branch (+TypeScript).
You don’t have those dependency issues anymore (once we publish new release)