Cannot find module './getBigInt'
See original GitHub issueApologies if this has been answered before or I’m just not understanding it, but memfs@^3.4.1
as a peer dependency of webpack-dev-middleware
has an issue where the lib/Stats.js fails to import ./getBigInt
– looking through node_modules/memfs
the getBigInt.js file is located at lib/src/getBigInt.js
instead of lib/getBigInt.js
Again, sorry if this has been addressed before or I’m not doing it right. Just wanted to see if this has been patched somewhere and I’m a little confused. For now I’ve reverted to 3.4.1 in my project’s package-lock.json
so we’re alright for now, but wanted to post this issue in here in case it was at all helpful. Thanks!
Issue Analytics
- State:
- Created a year ago
- Reactions:10
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Keep getting error "Cannot find module 'big-integer'" · Issue #15
Hi, I have installed nodejs with the version 10.15.3 as specified in the readme and I am running on Ubuntu 18.04. When doing...
Read more >Ask Question - Stack Overflow
An unhandled exception occurred: Cannot find module './browsers' - ; Did you do try to do npm install before ng serve ? ·...
Read more >Error: Cannot find module in JavaScript [SOLVED]
We can solve Error: Cannot find module by installing the missing module. We can use npm tool to install the mising module.
Read more >An unhandled exception occurred: Cannot find module ...
This short blog article shows you how to resolve the Angular error "An unhandled exception occurred: Cannot find module ...
Read more >cannot find module [Node npm Error Solved] - freeCodeCamp
In my case, I got it like this "Module not found: Error: Can't resolve 'react-icons/fa' in 'C:\Users\user\Desktop\Projects\Address Locator\ ...
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
🎉 This issue has been resolved in version 3.4.3 🎉
The release is available on:
Your semantic-release bot 📦🚀
I’ll try and look into this now but can’t give an ETA sorry - it might have to wait until at least the weekend