Closed johnpc closed 1 month ago
Thanks for the report. @inquirer/type@1.5.4
should've been a major; it's a human mistake.
It's always a bit tricky to then deal with history given the forward only nature of packages, but I think there's a fix out now.
@inquirer/type@1.5.3
is republished as 1.5.5
https://www.npmjs.com/package/@inquirer/type/v/1.5.5 (content seems correct.) I don't think that'll break the in-between versions relying on 1.5.4 - but luckily those were all major, so it should reduce the radius of impact.@inquirer/type@1.5.4
is republished as 2.0.0
, including patches release for all dependencies.Lastly, I made the dependencies within this monorepo strict, so it reduces the risk of that type of issue reoccurring. Thanks for the timely report!! This bug still up Monday would've caused a lot of headache 😬😱
Note: Will still accept help migrating this repo from lerna to changeset if someone wanna start a PR.
I am using AWS Amplify's CLI tool (
ampx
) which is installed vianpm
. Since the release of@inquirer/type@1.5.4
a couple hours ago, the CLI tool is unusable:I have confirmed that I am able to fix this issue by downgrading inquirer via
Full repro steps: