Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

current yarn.lock file is incompatible with node version 10.11.0 #7524

Closed
booo opened this issue Oct 31, 2018 · 3 comments
Closed

current yarn.lock file is incompatible with node version 10.11.0 #7524

booo opened this issue Oct 31, 2018 · 3 comments

Comments

@booo
Copy link
Contributor

booo commented Oct 31, 2018

mapbox-gl-js version: 999a8d9 (master)

browser: -

node.js version: v10.11.0

Steps to Trigger Behavior

  1. cd /tmp
  2. git clone https://github.com/mapbox/mapbox-gl-js
  3. yarn install

Excerpt from yarn output

... error upath@1.0.4: The engine "node" is incompatible with this module. Expected version ">=4 <=9". Got "10.11.0" error Found incompatible module ...

Expected Behavior

Yarn install should run without errors on node.js v10.11.0

Actual Behavior

Yarn fails to run properly because of an outdated yarn.lock

Proposed Solution

Update the yarn.lock file with yarn upgrade. What's your policy on updating the yarn.lock file? I can prepare a pull request with an update if you like.

@booo booo changed the title current yarn.lock file is incompatible node version 10.11.0 current yarn.lock file is incompatible with node version 10.11.0 Oct 31, 2018
@ryanhamley
Copy link
Contributor

Thanks for the report @booo We're working on it here #7519 Just investigating a couple of issues before merging it.

@ryanhamley
Copy link
Contributor

Ah, this is actually two slightly different issues. The yarn.lock file is now updated to reflect the change to JSDOM, but that wasn't what was causing the The engine "node" is incompatible with this module error. There appears to be a dependency somewhere installing upath@1.0.4 which is incompatible with Node 10. This issue was fixed in v1.0.5 of upath but whatever package is using it hasn't updated. We can run yarn upgrade to update all of our packages which results in the huge yarn.lock diff we tried to avoid in #7519. In the meantime, yarn upgrade or yarn --ignore-engines install both produce the desired result.

@booo
Copy link
Contributor Author

booo commented Nov 1, 2018

Yarn why upath should tell you by which package the upath is used.

As far as I understand the yarn upgrade documentation it should be possible to upgrade individual packages with e.g. yarn upgrade upath. See https://yarnpkg.com/lang/en/docs/cli/upgrade/

If you remove the first occurrence of upath in the yarn.lock file and run yarn install you get a minimal change to the yarn.lock file:

diff --git a/yarn.lock b/yarn.lock
index 2a764c96a..394bdc1ce 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -11949,12 +11949,7 @@ unzip-response@^2.0.1:
   resolved "https://registry.yarnpkg.com/unzip-response/-/unzip-response-2.0.1.tgz#d2f0f737d16b0615e72a6935ed04214572d56f97"
   integrity sha1-0vD3N9FrBhXnKmk17QQhRXLVb5c=
 
-upath@^1.0.0:
-  version "1.0.4"
-  resolved "https://registry.yarnpkg.com/upath/-/upath-1.0.4.tgz#ee2321ba0a786c50973db043a50b7bcba822361d"
-  integrity sha512-d4SJySNBXDaQp+DPrziv3xGS6w3d2Xt69FijJr86zMPBy23JEloMCEOUBBzuN7xCtjLCnmB9tI/z7SBCahHBOw==
-
-upath@^1.0.5:
+upath@^1.0.0, upath@^1.0.5:
   version "1.1.0"
   resolved "https://registry.yarnpkg.com/upath/-/upath-1.1.0.tgz#35256597e46a581db4793d0ce47fa9aebfc9fabd"
   integrity sha512-bzpH/oBhoS/QI/YtbkqCg6VEiPYjSZtrHQM6/QnJS6OL9pKUFLqb3aFh4Scvwm45+7iAgiMkLhSbaZxUqmrprw==

booo added a commit to booo/mapbox-gl-js that referenced this issue Nov 1, 2018
The current yarn.lock breaks the `yarn install` step on systems with
node v10.11.0 because upath version 1.0.4 requires the version of node
to be <= 9. Updating upath to 1.1.0 fixes the problem.

Addresses issue mapbox#7524.
mourner pushed a commit that referenced this issue Nov 1, 2018
…#7532)

The current yarn.lock breaks the `yarn install` step on systems with
node v10.11.0 because upath version 1.0.4 requires the version of node
to be <= 9. Updating upath to 1.1.0 fixes the problem.

Addresses issue #7524.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants