-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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] npm init seems broken #2206
Comments
Hello @outloudvi This only happens when you want to initialize with react-app or with other npm packages too? |
@p3javier I've tried |
@outloudvi I think that the issue is related with this commit 39ad1ad#diff-d5109920b34c2b2e141bd41232d8876432a17479c388e142d8a036bb7b36ea62 Could you make a fresh install of the version |
@p3javier Hi, I can confirm that |
So it seems that we catch the error! I will open a PR to review the changes made to anything that involves flatOptions between versions. |
There’s no need to open a PR to compare commits between tags. Since you’re saying v7.0.4 is fine, and v7.0.12 is not, perhaps you could do a binary search and determine in exactly which version it broke? |
The `flatOptions` property exposed by `lib/npm.js` should not be redefined. This fixes an error in `npm init` by just avoiding trying to override the property there. Fixes: npm#2206
Current Behavior:
Expected Behavior:
npm init
should generate the app with the boilerplate.Steps To Reproduce:
npm init react-app my-app
Environment:
Error log:
The text was updated successfully, but these errors were encountered: