What is the problem this feature will solve?
I think it would be beneficial to have a new field in the node.config.json to specifiy the node version with which the application should run. In case it is not satisfied the application will throw an error.
Whats the use case?
- Fix a node config strictly
- Allow security scanners to infer the Node.js version used in the application (right now if you dont have a dockerfile its not possible)
- Prevent mismatch between environment and user assumption
Why not package.json#engines
Package.json engines are for the consumer not the producer.
Also applications that are not going to be published dont need the engines field.
What is the feature you are proposing to solve the problem?
Add a "version" field to the node.config.json. It would require to parse semver etc...
What alternatives have you considered?
none
What is the problem this feature will solve?
I think it would be beneficial to have a new field in the
node.config.jsonto specifiy the node version with which the application should run. In case it is not satisfied the application will throw an error.Whats the use case?
Why not
package.json#enginesPackage.json engines are for the consumer not the producer.
Also applications that are not going to be published dont need the
enginesfield.What is the feature you are proposing to solve the problem?
Add a "version" field to the
node.config.json. It would require to parse semver etc...What alternatives have you considered?
none