AhmarZaidi opened a new issue, #110: URL: https://github.com/apache/age-viewer/issues/110
## Issue: When we install AGE-Viewer on a version of node that is not supported we simply get errors but not any warning beforehand. Although, it is suggested in the documentation that node versions ^14.16.0 are supported but it is not implemented in code where warnings can be generated by node. ## Solution: We can define the engines field in the package.json and set the range of tested versions there. This would give a warning when we try to install while on an untested version. If the solution is implemented in this way then we can use the engine-strict flag. This would simply generate an error on using incompatible versions. Additionally, if a user changes the node version after installing (say for some other project), then they would get to know very easily that its due to node/npm version. ## Links: [NPMJS Documentation on Engines in Package.json](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#engines) [Some more info on Package.json and engines](https://www.marcusoft.net/2015/03/packagejson-and-engines-and-enginestrict.html) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
