[Bug?]: @yarnpkg/[email protected] incompatible with {"npm":"8.3.1","node":"v16.14.0"}

[pdimova]

Describe the bug

Our project is using Lerna to run commands in the pipeline and it looks like after the last release we got the following error:

Is this a bug or an intended outcome?

To reproduce

N/A

Environment

cimg/node:16.14.0-browsers
[email protected]

Additional context

No response

[arcanis]

Is this a bug or an intended outcome?

Yes, we will remove Node 14/16 support in the next major, and this change has been published in RC (ie prerelease; not on stable channels yet). I don't know what depends on @yarnpkg/parsers in a prerelease version, but that seems something they should fix on their side.

[edmar-at-bit]

same issue our pipelines stopped working 3hrs ago

[arcanis]

As a very temporary workaround I marked @yarnpkg/[email protected] as deprecated on the registry, to avoid it being selected by the ^3.0.0-rc.18 range used by nx, but please open an issue there to ask them to remove the caret from the range as soon as they can.

[edmar-at-bit]

thanks @arcanis

[arcanis]

Weirdly, it seems the deprecated setting didn't work (in Yarn, we avoid using deprecated versions when others would work - it's strange npm doesn't do this, I kinda remember us adding this behaviour in part because we thought it did 🤔).

I manually published a 3.0.0-rc.47.1 that doesn't include the engines field, but upstream will still have to fix it before we make another automated release (nrwl/nx#17860).

[arcanis]

Note that another RC got released this week-end (we're working on release the 4.0 soon, so we need to regularly release RCs), so the engines field is back again.

The Lerna / nx fix got released in their 16.5.0-beta.1 release, but since it's a beta it's not pulled by default. Hopefully nx will solve that soon, in the meantime I will publish a workaround again, hopefully for the last time.

[edmar-at-bit]

Note that another RC got released this week-end (we're working on release the 4.0 soon, so we need to regularly release RCs), so the engines field is back again.

The Lerna / nx fix got released in their 16.5.0-beta.1 release, but since it's a beta it's not pulled by default. Hopefully nx will solve that soon, in the meantime I will publish a workaround again, hopefully for the last time.

i think they have it on NX v16.4.1, had to migrate my NX from v15 to v16.4.1 to make my pipeline running again

[yarnbot]

Hi! 👋

It seems like this issue as been marked as probably resolved, or missing important information blocking its progression. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it.