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.
No valid exports main found for 'listr2/node_modules/nanoid'
See original GitHub issueIt was reported in https://github.com/okonet/lint-staged/issues/870 that using Node.js version 13.6.0 listr2 fails to a nanoid import. The issue affects lint-staged because of the semver range allowing listr@2.0.3 to be installed. I assume this error is similar to https://github.com/cenk1cenk2/listr2/issues/25
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to fix “Error: No valid exports main found for ... - Dev Genius
The solution. After some digging around, I found the suggestion to update to Node 14.5. There are many ways to do this; I...
Read more >No valid exports main found for node_modules\uuid #5381
Hi, I just updated my project using npm -update @loopback/cli and lb4 update. No errors on build but when I start I get...
Read more >Error: No valid exports main found for (Module path)
I managed to fix the problem. Uninstall NodeJS, NPM and NVM | Here is how on Mac OS How do I completely uninstall...
Read more >How to fix “Error: No valid exports main found ... - Godwill Barasa
How to fix “Error: No valid exports main found for '/node_modules/packname by Godwill Barasa. On 12th May, as I was trying to “npm...
Read more >Fixing Create React App Error: No valid exports main found
If you're getting “No valid exports main found” in your Create React App, trying to install the latest version of NodeJS.
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
This problen with random id generation is interesting. I do not want to limit node version with a trivial dependency as this maybe it should be best to go back to working version of ^7 of uuid
🎉 This issue has been resolved in version 2.0.4 🎉
The release is available on:
Your semantic-release bot 📦🚀