Inquirer.js: Node V8 Support broken with 7.3.0
[email protected] is using [email protected] which does not support node v8
I think we should bump deps and upgrade to [email protected] dropping legecy node support while keep [email protected] work with old node
githoniel
All 2 comments
Sorry about this, it's really hard to track breaking old Node version when bumping library. You should use package-lock to make sure this doesn't happen if you run versions who're out of LTS.
Since Node 8 is out of LTS, I'll leave the package as is. Feel free to downgrade to the previous version.
SBoudrias
on 9 Jul 2020
This has broken installations of storybook 5.3, which supports node 8 and relies on inquirer@^7.0.0. Lock files are fine, but they're not sufficient for me who is trying to install that version of storybook into a project that is so far locked into node 8.
Please be a good citizen and follow semver. If you'd like to drop node 8 support, that's cool, but the right thing to do would be to release a new major version. There's no telling how many other packages and libraries might be broken by not doing so.
IanVS
on 14 Jul 2020
Related issues
Ezekiel-DA
路
7Comments
aydn
路
5Comments
PierBover
路
6Comments
mechanical-turk
路
3Comments
lvjiaxuan
路
6Comments
Most helpful comment
This has broken installations of storybook 5.3, which supports node 8 and relies on inquirer@^7.0.0. Lock files are fine, but they're not sufficient for me who is trying to install that version of storybook into a project that is so far locked into node 8.
Please be a good citizen and follow semver. If you'd like to drop node 8 support, that's cool, but the right thing to do would be to release a new major version. There's no telling how many other packages and libraries might be broken by not doing so.