Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
package.json causing error when running npm install
See original GitHub issueIssue Description
Hello everyone!
I’m new to cxjs, and I was looking into getting my developers into your framework. Looks like you guys have a lot of good stuff cooking up. Unfortunately I’m not able to grab master and install the dependancies, or get the Step by Step app to kick off properly.
Here is my error for cloning master:
npm ERR! argv "/Users/adamkpurdy/.nvm/versions/node/v7.2.1/bin/node" "/Users/adamkpurdy/.nvm/versions/node/v7.2.1/bin/npm" "install"
npm ERR! node v7.2.1
npm ERR! npm v3.10.10
npm ERR! Unsupported URL Type: link:./packages/cx
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /Users/adamkpurdy/Sites/samples/react-box/cx-box/cxjs/npm-debug.log
Looks like line 96 in the package.json file.
**The Step by Step instructions in the docs for the getting-started app is also falling to start:
npm ERR! Darwin 16.7.0
npm ERR! argv "/Users/adamkpurdy/.nvm/versions/node/v7.2.1/bin/node" "/Users/adamkpurdy/.nvm/versions/node/v7.2.1/bin/npm" "start"
npm ERR! node v7.2.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! cx-getting-started@1.0.0 start: `webpack-dev-server --open`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the cx-getting-started@1.0.0 start script 'webpack-dev-server --open'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cx-getting-started package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! webpack-dev-server --open
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs cx-getting-started
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls cx-getting-started
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/adamkpurdy/Sites/samples/react-box/cx-box/cx-getting-started/npm-debug.log
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
npm install gives error "can't find a package.json file"
Now you have to cd to your project folder. Now npm install should work now, if not, then you have another issue. Save...
Read more >Common errors | npm Docs
Invalid JSON · Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later. · This...
Read more >NPM install error - Material Design for Bootstrap
Hi! You can try to: 1. Delete your node_modules catalog and package-lock.json file 2. Run npm cache clean ...
Read more >How to solve npm ERR! code 1 when running npm install
This cause of this error is that one of the dependencies you define in your package.json file fails to be installed properly on...
Read more >5 Ways to Fix the Npm Install Not Working Issue
The main cause of the npm command not found error is that npm is not installed. You can run the command “npm -v”...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems that npm changed their plan and decided to use
file:instead oflink:for symlinks.https://github.com/npm/npm/pull/15900 https://github.com/yarnpkg/yarn/issues/4212
We must choose between yarn or npm.
file:is supported by both, but behaves differently. In favor of yarn, I would really like to try out workspaces and yarn upgrade-interactive is a life saver.I think Adam was referring to
npm install, and indeed it breaks even with the latest version of Node, even though it comes withnpm 5.3.0:So, for now it’s best to use
yarn installor justyarn. Adam, you can get the yarn package manager here: https://yarnpkg.com/en/