[NPMCLI-179] Inform users of outdated version of Node Created: 16/Apr/18  Updated: 25/Mar/22

Status: Open
Project: Magnolia CLI
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to NPMCLI-188 mgnl jumpstart not working on centos 7 Closed
duplicate
is duplicated by NPMCLI-187 mgnl jumpstart : Error: Object.value... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Starting is easy
Story Points: 1

 Description   

Users get errors when their installed version of Node is not recent enough for some feature in the CLI. The error messages give no clue to what the problem is. This has happened several times internally already.

Research and devise a practice for our CLI to ensure that users get clear instructions when they need to update their node version. 

To consider/options:

  • Probably we need to explicitly declare a Node version dependency for the whole CLI - either in package.json, or through another means. Preferred.
  • If we need to set requrired versions somewhere - then document this process and add it to a release QA checklist for the CLI.

Acceptance Criteria

  • Upon installation of a new CLI version, inform user if node update is required.
  • Upon execution of any command, warn user if update is required. (We dont need a separate check for each command - just the one check if the current node version is supported or not.)

Generated at Mon Feb 12 04:47:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.