-
Story
-
Resolution: Unresolved
-
Major
-
None
-
3.0.1
-
None
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.)
Acceptance criteria
- is duplicated by
-
NPMCLI-187 mgnl jumpstart : Error: Object.values is not a function
- Closed
- relates to
-
NPMCLI-188 mgnl jumpstart not working on centos 7
- Closed