question-mark
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.

Maybe what I’m doing wrong is obvious to experienced npm users. I just cloned the repo, cd’d to it, and ran npm i:

npm-debug.log.txt

tsickle$ npm i npm WARN package.json tsickle@0.1.7 No bin file found at build/src/main.js npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated lodash.isarray@4.0.0: This package is deprecated. Use Array.isArray. npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated lodash@1.0.2: lodash@❤️.0.0 is no longer maintained. Upgrade to lodash@^4.0.0. npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use ‘npm ls graceful-fs’ to find it in the tree. npm WARN peerDependencies The peer dependency typescript@>=1.7.3 included from tslint will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. \

tsickle@0.1.7 prepublish /usr/local/google/src/tsickle gulp compile

[16:41:33] Using gulpfile /usr/local/google/src/tsickle/gulpfile.js [16:41:33] Starting ‘compile’… [16:41:35] Finished ‘compile’ after 2.49 s npm ERR! Linux 3.13.0-95-generic npm ERR! argv “/usr/local/google/home/tbreisacher/.nvm/versions/node/v4.4.7/bin/node” “/usr/local/google/home/tbreisacher/.nvm/versions/node/v4.4.7/bin/npm” “i” npm ERR! node v4.4.7 npm ERR! npm v2.15.8 npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package typescript@2.1.0-dev.20160827 does not satisfy its siblings’ peerDependencies requirements! npm ERR! peerinvalid Peer tslint@3.15.1 wants typescript@>=1.7.3 npm ERR! peerinvalid Peer gulp-typescript@3.0.2 wants typescript@~2.0.3 || >=2.0.0-dev || >=2.1.0-dev

npm ERR! Please include the following file with any support request: npm ERR! /usr/local/google/src/tsickle/npm-debug.log

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
evmarcommented, Oct 5, 2016

Try syncing, rm -rf node_modules, and npm i again.

1reaction
MatrixFrogcommented, Oct 4, 2016

tsickle$ npm i typescript npm ERR! Linux 3.13.0-95-generic npm ERR! argv “/usr/local/google/home/tbreisacher/.nvm/versions/node/v4.4.7/bin/node” “/usr/local/google/home/tbreisacher/.nvm/versions/node/v4.4.7/bin/npm” “i” “typescript” npm ERR! node v4.4.7 npm ERR! npm v2.15.8 npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package typescript@2.0.3 does not satisfy its siblings’ peerDependencies requirements! npm ERR! peerinvalid Peer tslint@3.15.1 wants typescript@>=1.7.3 npm ERR! peerinvalid Peer gulp-typescript@3.0.2 wants typescript@~2.0.3 || >=2.0.0-dev || >=2.1.0-dev

npm ERR! Please include the following file with any support request: npm ERR! /usr/local/google/src/tsickle/npm-debug.log

Read more comments on GitHub >

github_iconTop Results From Across the Web

Common errors | npm Docs
It's most likely a temporary npm registry glitch. Check npm server status and try again later. · If the error persists, perhaps the...
Read more >
npm install error from the terminal - Stack Overflow
Running just "npm install" will look for dependencies listed in your package.json. The error you're getting says that you don't have a package.json...
Read more >
5 Ways to Fix the Npm Install Not Working Issue
Way 1. Make Sure Npm Is Installed ... The main cause of the npm command not found error is that npm is not...
Read more >
NPM install error - Material Design for Bootstrap
Trying to install MDB pro 4.19.2 just downloaded and ran npm install but getting this error of sha512 not matching. Can someone tell...
Read more >
Common Errors - npm - w3resource
Common Errors · It is most likely a temporary npm registry glitch. Check your npm server status and then try again. · If...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found