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.

cosmiconfig requires at least version 4 of Node, please upgrade :'4' < '8.99' true '4' < '10.xx' false

See original GitHub issue
var index$48 = function (pkg) {
  var requiredVersion = pkg.engines.node.replace(">=", ""); // '4'
  var currentVersion = process.version.replace("v", ""); // '10.x'  '11'
  if (currentVersion < requiredVersion) {
    console.error(
      "%s requires at least version %s of Node, please upgrade",
      pkg.name,
      requiredVersion
    );
    process.exit(1);
  }
};
index$48()

Issue Analytics

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

github_iconTop GitHub Comments

2reactions
aghArdeshircommented, Mar 4, 2019

(…continued from post above)

Which is actually seems to be solved in prettier@1.7.1 and I only needed to npm i -D prettier@1.7.1.

But how are everyone expect to solve this? Like me step through CHANGELOG.md? Isn’t there a service like npm audit but for this kind of things. like found 1 error in your build system (1 awful, 0 moderate, 0 low). run npm wtf fix to fix them, or npm wtf for details. and when I run npm wtf I get:

Hey, your build system depends on prettier@1.7.0 which depends on an awful cosmiconfig/please-upgrade-node version which breaks your build system. upgrade to (at least) prettier@1.7.1 for fix and also consider these breaking changes:

  • <considerations of breakingChange 1>
  • <considerations of breakingChange 2>
  • <considerations of breakingChange 3>
  • <considerations of breakingChange 4>

That would be awesome 😃 @zkat

0reactions
aghArdeshircommented, Mar 4, 2019

@j-f1

Hello! I have this issue & I have ^1.7.0 in my package.json which is resolved to:

"prettier": {
      "version": "1.7.0",
      "resolved": "https://registry.npmjs.org/prettier/-/prettier-1.7.0.tgz",
      "integrity": "sha512-kIbA3UE9sYGiVCxlWg92EOHWZqte6EAkC7DS5je6NaL8g3Uw1rWe0eH+UX4Hy5OEiR9aql2vVMHeg6lR4YGxYg==",
      "dev": true
    },

package-lock.json

and when I search in prettier’s package source code, I see: "please-upgrade-node":"^3.0.1"

Read more comments on GitHub >

github_iconTop Results From Across the Web

Node version needs upgrading?? but its higher than what its ...
The current version of @vue/cli-service requires "node": "^12.0.0 || >= 14.0.0". but the error message doesn't show that for some reason.
Read more >
From v27 to v28 - Jest
Upgrading Jest from v27 to v28? This guide aims to help refactoring your configuration and tests.
Read more >
license_scanning (#2758) · Jobs · osm / NG-UI · GitLab
Returns null if there is no such active transition on the specified node. This method is useful for creating chained transitions.
Read more >
Upgrade from v0.6.1 to v1.17.0 (latest) - NodeBB
For this method when I run "nodebb start" or "nodebb upgrade -s" getting ... versions of Node.js npm WARN deprecated minimatch@0.3.0: Please ......
Read more >
The newest update to 2.x. Cocos Creator 2.4.10 is available
We will continue to provide critical bug fixes through 2022, as planned, for the official release of version 3.0. These fixes will be...
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