More accurate explanation of recommended version is needed in v5 release note.
See original GitHub issueExpected Behavior
More accurate explanation of recommended version is needed in v5 release note.
Current Behavior
In v5.0.0 release note, explain recommend version.
Node v10.x and v12.x are no longer supported.
Please upgrade to the latest LTS release of Node (we recommend either v14 or v16).
But actual warning message shows more accurate version. (In my case, using Node 14.15.4)
The engine "node" is incompatible with this module. Expected version "^14.19.3 || >=16.0.0". Got "14.15.4"
Context
So I suggest fix recommend version more accurately (^14.19.3)
Your Environment
Executable | Version |
---|---|
lerna --version |
5.0.0 |
node --version |
14.15.4 |
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
Unreal Engine 5.0 Release Notes
Overview of new and updated features in Unreal Engine 5.0.
Read more >VMware SASE 5.0.0 Release Notes
The release notes cover the following topics: Recommended Use; Compatibility; Upgrade Paths for Orchestrator, Gateway, and Edge; Important Notes ...
Read more >Security Management System Release Notes - Trend Micro
Security Management System. Release Notes. Version 5.5. To ensure that you have the latest versions of product documentation, visit the Online Help Center....
Read more >QTS 5.0.1 | Release Notes | QNAP (US)
You should also see Important Notes before updating QTS. What's New. Replace a RAID Disk with a Spare Before Potential Failure. Enhanced transfer...
Read more >Release Notes for Cisco HX Data Platform, Release 5.0
For more information see the Cisco HyperFlex Data Center without Fabric Interconnect Installation. Supported Versions and System Requirements ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@nelson6e65 Yes. i know However, after reading the release note of v5.0.0, I thought it didn’t matter. Because minimum version was v14 and i thought v14 meant minor version of all v14.
My suggestion is that more accurate information should be displayed in the release notes. So, the description of changing the recommended version should not be
recommended either v14 or v16
(above sentence), butrecommended either v14.19.3 or v16
.LTS doesn’t mean no more features Some packages may rely on features which has been added into Node newer versions and backported in a minor patch into previous Node version Eg. this happened for ESM support and many projects have a min Node version which is a late patch version of the v12 LTS