[Bug?]: Prolog constraints isn't deprecated - they doesn't exist anyone

[asvishnyakov]

Self-service

• I'd be willing to implement a fix

Describe the bug

Yarn doesn't take into account engines: node from package.json regardless enableConstraintsChecks. This is because this contstraints wasn't "deprecated" as said here, they was completely removed.

To reproduce

1. Clone project with engines: node in package.json
2. Run yarn 4.x

Environment

System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
  Binaries:
    Node: 20.11.0 - C:\Users\ALEKSA~1\AppData\Local\Temp\xfs-2d7894a2\node.CMD
    Yarn: 4.0.2 - C:\Users\ALEKSA~1\AppData\Local\Temp\xfs-2d7894a2\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD

Additional context

No response

[merceyz]

The constraints it's referring to is https://yarnpkg.com/features/constraints, not the engines field.

[asvishnyakov]

@merceyz @arcanis But engines worked on yarn 3.x and doesn't work on yarn 4.x. Why?

[merceyz]

That's surprising to see as we never implemented it, see #1177.

[asvishnyakov]

@merceyz Wow! Just installed yarn 3.x and it doesn't appear. So it's really surprising and means something did it "on behalf" of yarn. Really interesting. Thank you for the information and sorry for inconvenience!