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.

Error installing with Yarn (node >=6.9 required)

See original GitHub issue

Subject of the issue

Since 2.13, engine in the package.json as been set to node 6.9 (released in october…). Had to update the global version of node.js. It makes yarn fail the install and throw this error :

yarn

yarn install v0.16.1 info No lockfile found. [1/4] 🔍 Resolving packages… [2/4] 🚚 Fetching packages… error angular-translate@2.13.0: The engine “node” is incompatible with this module. Expected version “>=6.9”. error Found incompatible module info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

npm ERR! Darwin 16.1.0 npm ERR! argv “/usr/local/Cellar/node/6.8.0/bin/node” “/usr/local/bin/npm” “run” “yarn” npm ERR! node v6.8.0 npm ERR! npm v3.10.8 npm ERR! code ELIFECYCLE npm ERR! 1001backend@0.0.0 yarn: yarn npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the 1001backend@0.0.0 yarn script ‘yarn’. 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 1001backend package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! yarn npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs 1001backend npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls 1001backend npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /Users/romainb/Code/1001backend-dev/npm-debug.log

npm ERR! Darwin 16.1.0 npm ERR! argv “/usr/local/Cellar/node/6.8.0/bin/node” “/usr/local/bin/npm” “run” “super-install” npm ERR! node v6.8.0 npm ERR! npm v3.10.8 npm ERR! code ELIFECYCLE npm ERR! 1001backend@0.0.0 super-install: npm run yarn-install && npm run yarn npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the 1001backend@0.0.0 super-install script ‘npm run yarn-install && npm run yarn’. 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 1001backend package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm run yarn-install && npm run yarn npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs 1001backend npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls 1001backend npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /Users/romainb/Code/1001backend-dev/npm-debug.log

Your environment

  • version of angular-translate : 2.13.0
  • version of angular 1.5.8

Steps to reproduce

Have yarn, node >6.9 and try yarn add angular-translate@2.13.0

Expected behaviour

Should install angular translate

Actual behaviour

Crash, saying node should be “>=6.9”

Issue Analytics

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

github_iconTop GitHub Comments

2reactions
knallicommented, Nov 11, 2016

Alternatively we remove the engine part (only in package.json, we have to leave it for nvm and travis). That’s not perfect, but perhaps more comfortable?

2reactions
knallicommented, Nov 11, 2016

Rephrasing my post 4 days ago: This is primarily a dev-stack runtime. I (role of a package owner) simply do not care of older versions within my dev stack flow.

That is a little bit curious, because this package actually do not have any requirement to the npm/node environment (mainly a browser env target package).

Said that, the dependency is given out because we publish this package to npm directly. Maybe we have to consider making a dedicated package.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error Codes | Yarn - Package Manager
This informational message occurs when Yarn wishes to let you know that a package will need to be built for the installation to...
Read more >
A Comprehensive Guide to Fixing Node-Gyp Issues on Windows
1. Try running npm install with the --no-optional flag. ... If you're lucky, the dependency that requires node-gyp will be optional, and you...
Read more >
NPM or Yarn errors on fresh 5.3 install - Laracasts
However, everything seems to run just fine with node 6.9.1. I rolled back to yarn 0.16.1 with node 6.9.1 and everything works without...
Read more >
Node.js Buildpack | Cloud Foundry Docs
js buildpack, run npm install (or yarn install , if you are using Yarn) from your app directory. This command vendors dependencies into...
Read more >
Prevent npm install for not supported Node.js versions
Use a local npm configuration to prevent users from installing your ... Yarn doesn't need an additional configuration file and treats the ...
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