Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
9.1.6. Cannot find module '@babel/helper-create-regexp-features-plugin'
See original GitHub issueBug report
After upgrading to Next 9.1.6 I am having a problem running my next js server locally. I get
./resources/images/logo.svg
Error: Cannot find module '@babel/helper-create-regexp-features-plugin'
Describe the bug
The problem with @next/bundle-analyzer latest, if I keep Next 9.1.6 and @next/bundle-analyzer 9.1.5 everything work fine.
Screenshots
System information
- OS: macOS
- Browser: all
- Version of Next.js: 9.1.6
Additional context
Also I have used @svgr/webpack
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
drupal 9.1.6 | Drupal.org
This is a patch (bugfix) release of Drupal 9 and is ready for use on production sites. Learn more about Drupal 9. Drupal...
Read more >Error: Cannot find module 'nanoid/non-secure' - Stack Overflow
I just had the same issue. Try checking if you're installing the node module in the correct directory, i.e. where you're writing the...
Read more >Description - SiteKiosk
Hello Support. I check the nodelog file and found there is an error there - "Cannot find module ../build/Release/bson"
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
@c0b41 thanks, I have deleted
node_modulesand reinstall, the problem was fixed.Is there a programmatically way to fix it, I have a devops flow that sometimes breaks cause of this error… if I do a empty commit again it works