-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[BUG] Error: bad marker at ConfigChain.add
using fnm with node v12.14.1
#1660
Comments
Yeah, we encountered this in the CITGM tests just recently, I was wondering if anyone would run into that race condition outside of CITGM. Currently in the middle of clearing out all the old code in In the meantime, the best approach is probably to have nvm reinstall node 12.14.1 so you get a fresh v6 version. |
Ok I guess I that was bad luck for me 😄 I managed to reinstall npm from another open shell in the end so all good. |
I'm facing the same issue on Windows. Uninstalling and re-installing NodeJS doesn't revert the npm to v6. What would be the way to revert npm on Windows? |
@AakashM maybe deleting the folders manually and then reinstalling could help. |
@isaacs This is still happening on v7.0.0-beta5, breaking exactly like in beta4.
Environment:
|
Yes, I know. It's fixed by #1688, just landed today, which will be in beta.6. You can |
Current Behavior:
When running npm or npx this error happens:
Expected Behavior:
npm should be usable
Steps To Reproduce:
Environment:
The text was updated successfully, but these errors were encountered: