v4.0.0-alpha.0 is released as `latest`
mariuslundgard opened this issue · comments
Issue description or question
Since v4.0.0-alpha.0 is tagged as latest on npm, there’s a mental burden when updating projects.
yarn outdated will show that the package needs an update, while it’s not desirable to upgrade to an alpha version (in my case at least).
This is still an issue. Why is the alpha version being advertised as @latest?
@chrisblossom @johnagan Agreed, and is there a release plan for v4.0.0? The last release was more than two years ago.
Any news on this?
What are the breaking changes in this release? There's no changelog or release notes.
looking at the diff I think the answer is:
Breaking changes:
- Dropped support for NodeJS 8
- Dropped support for webpack 3
Changes
- Added support for NodeJS 14
- Added support for webpack 5