-
-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: update @inquirer/confirm
to 4.0
#2300
Conversation
@inquirer/confirm
to 4.0
Hi, @greysteil 👋 Thanks for submitting this. I think this looks great. |
@inquirer/confirm
to 4.0@inquirer/confirm
to 4.0
Publishing it as a fix. No user-facing changes present. |
Released: v2.4.13 🎉This has been released in v2.4.13! Make sure to always update to the latest version ( Predictable release automation by @ossjs/release. |
It looks like we still need one more bump to |
@ravicious sounds good. Pull requests are welcome! |
All yours @ravicious (or I'll take it if you're busy) |
I have to yield as I don't have enough free time at work to take care of this, but I do appreciate your effort! |
Done in #2325 |
The only change between v3 and v4 is allowing the prefix for the confirm message to be changed, which msw doesn't use. (Alternatively we could widen the supported range here to
^3.0.0 || ^4.0.0
, but it looks like msw generally specifies a single major version it supports.)The main benefit of the change will be to get access to SBoudrias/Inquirer.js#1569 once it lands (or to make it easier to do so if that is released in a new major version). That will reduce development build size for lots of apps which are currently getting two versions of
@types/node
due to this dependency.