-
Notifications
You must be signed in to change notification settings - Fork 147
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
Running npm init
inside a folder with a space doesn't work as expected
#72
Comments
seems like #71 would fix this |
And that was merged. @cinderblock do you still face this issue? |
|
Issue still exists |
Issue still exists |
I think #81 may have fixed this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I like storing projects in folders with spaces in the name. I know this is not compatible with npm's project naming conventions but I still feel like this should not prevent
npm init
from working at all.As it stands, if you run
npm init
inside a folder with a space, it prints an error and refuses to prompt for anything besides the "complete" file, which is anything but complete.Steps to reproduce
And then npm will error:
Expected Results
No error. Not a nearly empty package.json. I'd expect to be prompted with which name I'd like to use and appropriate handlers if I specify a space. As in, similar to the old behavior from
4.2.0
.Environment
Tested on Windows 10 with npm version
5.0.3
and5.3.0
. Also tested with linux.Does not error on npm version
4.2.0
The text was updated successfully, but these errors were encountered: