Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4f7ad4f) to head (fdf63fc).
Report is 8 commits behind head on master.

@@            Coverage Diff            @@
##            master      #744   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          238       243    +5     
  Branches        48        49    +1     
=========================================
+ Hits           238       243    +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@purplecabbage what are your thoughts on placing this check here? Also, do we want a more generic error message that maybe links to the docs about supported version so this file doesn't become a dependency that needs to get updated every year when we add support for the next version?

Would love to get some feedback on the verbiage used here. I couldn't find devdocs that point to supported node versions, hence added the link to nvm documentation.
The reason(s) why the check was placed there
(i) By adding the check in src/index.js, we can make sure it runs at the earliest possible stage of CLI execution before any commands are processed
(ii) Also I thought that by placing it in the run method allows the execution to continue while creating a non-intrusive warning to the users

This is good, I would avoid using the term Adobe I/O anywhere new as we have sort of abandoned it ( even though it IS the aio cli ... )
It might be easiest to just cut it off with "... which is not officially supported." or "Warning: Node version ${nodeVersion} not supported."

@dthampy regarding your question about how best not to create future work
This might be an opportunity to be more specific with our supported node engines in package.json

"engines": {
  "node": "^18 || ^21 || ^22"
},

Then instead of looking just for >22 you could do:

const nodeVersion = process.version
if (!semver.satisfies(nodeVersion, config.pjson.engines.node)) {
  // output warning
}

@pru55e11 @purplecabbage
Simplified the warning to just show the relevant text.
Also now using the Config object to take care of reading and parsing the package.json file. Updated the unit tests as well