According to the package.json, node versions >=18 are supported.
When I execute an aio command using node22, I do not want to get a punycode warning.
Actual Behaviour
However, when executing aio plugins I get a warning
$ aio plugins
(node:32423) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Known details:
the punycode comes in through eslint(even latest 9.13.0) and @adobe/eslint-config-aio-lib-config that both use ajv
│ ├─┬ ajv@6.12.6
│ │ ├── fast-deep-equal@3.1.3 deduped
│ │ ├── fast-json-stable-stringify@2.1.0
│ │ ├── json-schema-traverse@0.4.1
│ │ └─┬ uri-js@4.4.1
│ │ └── punycode@2.3.1
Expected Behaviour
According to the package.json, node versions >=18 are supported. When I execute an aio command using node22, I do not want to get a punycode warning.
Actual Behaviour
However, when executing
aio plugins
I get a warningKnown details: the punycode comes in through eslint(even latest 9.13.0) and @adobe/eslint-config-aio-lib-config that both use ajv │ ├─┬ ajv@6.12.6 │ │ ├── fast-deep-equal@3.1.3 deduped │ │ ├── fast-json-stable-stringify@2.1.0 │ │ ├── json-schema-traverse@0.4.1 │ │ └─┬ uri-js@4.4.1 │ │ └── punycode@2.3.1
I tried to workaround it by using https://github.com/andreinwald/uri-js-replace but failes to do so.