balderdashy / balderdashy/sails

NPM errors while creating a new sails project by the command : sails new test-project

Open
#4,479 11 comments 0 reactions 0 assignees View on GitHub
try this out please
Dominant language
JavaScript
Stars
22.8k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

**Sails version**: 1.0.2
**Node version**: 8.11.3
**NPM version**: 5.6.0
**DB adapter name**: N/A
**DB adapter version**: N/A
**Operating system**: Windows 10


I am very new to sails js. I just installed sails globally on my local machine and when I try to create a new project with the command "sails new test-project", it just fails. And it fails everytime, the error is somewhere with NPM. Following is the verbose from the command prompt.

Press CTRL+C to cancel.
(to skip this step in the future, use --fast)
------------------------------------------------------------
Failed to install dependencies.
New app was generated successfully, but some dependencies
in node_modules/ are probably still incomplete or missing.

Before you continue, please make sure you are connected to the
internet, and that your NPM registry hasn't gone down.
Then cd into the new app and run:
rm -rf node_modules && npm install

See below for complete error details.
For more help, visit https://sailsjs.com/support.

error: { Error: Command failed: npm install
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/sails failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\admin\AppData\Roaming\npm-cache\_logs\2018-07-29T07_00_58_966Z-debug.log

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12) killed: false, code: 1, signal: null, cmd: 'npm install' }

Please suggest!!

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `sails new test-project` on Windows 10 with the reported Node.js 8.11.3 and npm 5.6.0 versions. Read the `npm install` output, especially the ENOTFOUND request to registry.npmjs.org and the proxy/network guidance. Done means determining whether Sails can address this failure or whether it is solely an npm connectivity problem.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.