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

Why new minor version 7.3.6 is incompitable with node 13.14.0 #447

Closed
1 task done
EliseevNP opened this issue Apr 7, 2022 · 7 comments · Fixed by #448
Closed
1 task done

Why new minor version 7.3.6 is incompitable with node 13.14.0 #447

EliseevNP opened this issue Apr 7, 2022 · 7 comments · Fixed by #448
Labels
Bug thing that needs fixing Needs Triage needs an initial review

Comments

@EliseevNP
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

error semver@7.3.6: The engine "node" is incompatible with this module. Expected version "^10.0.0 || ^12.0.0 || ^14.0.0 || >=16.0.0". Got "13.14.0"

Expected Behavior

It's should be compitable or new version should be 8.0.0

Steps To Reproduce

  1. In this environment...
  2. With this config...
  3. Run '...'
  4. See error...

Environment

  • yarn: v1.22.4
  • npm:
  • Node: 13.14.0
  • OS:
  • platform:
@EliseevNP EliseevNP added Bug thing that needs fixing Needs Triage needs an initial review labels Apr 7, 2022
@kburton
Copy link

kburton commented Apr 7, 2022

Additionally, lru-cache ^7.4.0 is not compatible with node 10.

@ljharb
Copy link

ljharb commented Apr 7, 2022

Indeed; v7.0.0 had no engines declaration at all, v7.1.0 set it to >= 10, and v7.3.6 was a breaking change both for changing engines.node and for upgrading lru-cache to v7.

This was referenced Apr 7, 2022
@ireinhart
Copy link

Same here... is #434 the issue?

@ljharb
Copy link

ljharb commented Apr 7, 2022

@ireinhart i don't think so; #442 and #433 certainly are though.

@pjohnmeyer
Copy link
Contributor

@archm49 I'm not sure why I was @-ed into this so I'm unsubscribing; you'll need to @-me again w/ some context if I'm expected to participate

@manjeetbrar91
Copy link

facing same issue. or production deployment stuck due this issue. please provide solution.

@pbadenski
Copy link

Sure this shouldn’t be a patch version change, but if you’re still on a non-maintained odd-numbered version 1.5 years after EOL you should really revisit your security processes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs an initial review
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants