yarn berry not check engines.node when do yarn run script?

[zyf0330]

I use yarn version 3.2.0 and node v16.17.0, and has package.json like this

...
  "scripts": {
    "e": "which node ",
},
  "engines": {
    "yarn": ">=3.2.0",
    "node": ">=14.0.0 <=14.18.1",
    "npm": "use yarn"
  },
...

When I run yarn run e, I expect that yarn gives an error because of bad node version, but it doesn't.
So when engines.node is effect?

[jj811208]

As far as I know yarn berry core does not handle engines of package.json, However, there are some third-party plugins that provide this

see: #1177

[merceyz]

See #1177

[hanseltime]

I'd like to suggest that this is added to the core yarnpkg. On the grounds that this:

1. is baseline functionality that was depended on in yarn 1 and is implicitly expected by any developer performing the migration
2. can actually affect the implementation of node packages that do binary compilation (and even more so with plug and play). This will degrade the usefulness of the package manager as engines continue to upgrade into the future.