Why npm init is not working - ubuntu 14.04 lts Ask Question Asked 4 years ago Active 4 years ago Viewed 743 times 1 npm init is not creating the package.json file. 3.
The first prompt, as shown in your screen capture, asks you to enter a package name. your coworkers to find and share information.
It works now.Yah! and i just confirmed on the repo that the errors where fixed since the ``8.2.0 release, which makes you the only one having the problem so far. initializer in this case is an npm package named create-
I have tried pressing … Ask Question Asked 3 years ago. I have found that the best way to learn node and npm is to ask questions, because the tutorials are too assuming. You can just hit There are two ways to create a empty package.json file:and it will create the package.json file in the dir where you run the command and will display the code shown bellow:I am new on npm. The upstream PR has already been merged and will be included in the next version of node; which should be releasing today.I think this can be closed now, it has been fixed in Node v8.1.1/v8.1.2.Guys I get the same error but giving the npm init command on git bash works fine for me..Try itSuccessfully merging a pull request may close this issue. The Overflow Blog Stack Overflow works best with JavaScript enabled I struggled with this, too. As with npm init, the npm install command has a flag or two that you'll find useful in your workflow - it'll save you time and effort with regard to your project's package.json file. Check npm’s proxy configuration. Featured on Meta Linux 64bitSame here: Hangs on version number question and can't input any text or do exit except by closing window.Same problem with npm 5.0.3 and node v8.1.0. Because npm init has to be able to create package.json file in a directory that you run it in. Manually go into the AppData directory and you will find that there is no npm directory inside Roaming. Stack Overflow works best with JavaScript enabled It would be easier to downgrade, if you have used a nvm (Node Version Manager) for installing node.I'm using Window OS and I turn off controlled folder access. By clicking “Post Your Answer”, you agree to our To subscribe to this RSS feed, copy and paste this URL into your RSS reader. ; This can be caused by corporate proxies that give HTML responses to package.json requests.
npm was installed with the mac package (but i also tried replacing with brew install) node itself works fine. However to by-pass and create the package.json file you can use the Alright, it seems to be a bug in 8.1.0 and will be fixed in Tuesday's release.The fix for this issue is already in progress and should be implemented in Yes, I also faced this issue, so you can downgrade the node to LTS version. so try VS Code or IDE you all use to Generally, it is not required for installing packages. Active 4 years ago. site design / logo © 2020 Stack Exchange Inc; user contributions licensed under Manually create this directory.Thanks for contributing an answer to Stack Overflow! 4 comments Labels.
I have tried pressing enter or quitting with ^C but nothing happens.
By clicking “Post Your Answer”, you agree to our To subscribe to this RSS feed, copy and paste this URL into your RSS reader. site design / logo © 2020 Stack Exchange Inc; user contributions licensed under