You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm added support for the "devEngines" field recently. It works very similar to the engines field, but eslint-plugin-n has no support for it and does not pick it up from the package.json.
It would be cool, if the plugin could also take the "devEngines" field into account, for the calculation of the node.js version range.
eslint-plugin-n version
17.5.1
What problem do you want to solve?
npm added support for the "devEngines" field recently. It works very similar to the engines field, but eslint-plugin-n has no support for it and does not pick it up from the package.json.
It would be cool, if the plugin could also take the "devEngines" field into account, for the calculation of the node.js version range.
npm documentation: https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines
What do you think is the correct solution?
"devEngines" is read from the package.json and taken into account for the node.js version range calculation
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: