Package version 7.15.3 has a node engine version breaking change

Hi, I noticed that in the engines section in package.json changed:

from:

```
"engines": {
"node": ">=12.0"
},
```

to:

```
"engines": {
"node": ">=18.0"
},
```

This can be considered a breaking change as it can break package install for dependant packages.

We had a problem with running [cy2](https://www.npmjs.com/package/cy2):
```
yarn global add cy2@4.0.6
cy2 run --browser chrome --parallel ....
```

The above script started failing two days ago as our CI agent as it runs node with version 16.x.x.

The error that we got was:
> error roarr@7.18.3: The engine "node" is incompatible with this module. Expected version ">=18.0". Got "16.18.1"

in the end for us the fix was to use yarn `--ignore-engines` install flag.

I noticed that npm just issues a warning but executes the script.

Start with package.json and compare the engines entry for version 7.15.3 against the earlier >=12.0 requirement. Reproduce the reported yarn global add cy2@4.0.6 failure with Node 16.18.1, and verify that the intended Node support and installation behavior are consistent. Done means the Node 16 compatibility problem is addressed or the supported range is clearly established.

Written by the indexing model from the issue text.