[BUG] CLI will not install due to broken dependencies

[stephenbarreca]

Describe the bug.

CLI will not install due to new versions of downstream dependency, @asyncapi/generator, being broken.

Attempts to install the cli return the following error.

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @asyncapi/generator-hooks@0.1.1.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

Attempts to install previous versions of the CLI result in the same error.

Expected behavior

The CLI should install without issue. Upgrades to downstream dependencies should not break existing versions of this CLI.

Screenshots

How to Reproduce

1. Try and install the cli and call the help

npx --loglevel=error --yes @asyncapi/cli --help

🖥️ Device Information [optional]

• Operating System (OS):
• Browser:
• Browser Version:

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

No, someone else can work on it

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[jwilmoth-ehs]

https://www.npmjs.com/package/@asyncapi/generator-hooks shows only one version (0.1.0).

[stephenbarreca]

Seems to be caused by this bug in @asyncapi/generator@3.4.0, asyncapi/generator#2201

[c19yamamoto]

@stephenbarreca
Since the upstream issue asyncapi/generator#2201 has been resolved, this one should be resolved as well.

[stephenbarreca]

@stephenbarreca
Since the upstream issue asyncapi/generator#2201 has been resolved, this one should be resolved as well.

Not really. The underlying issue is still present. A downstream upstream dependency releasing a new version broke years worth of releases for this CLI tool. That is a big problem.

[c19yamamoto]

@stephenbarreca

Fair point. The CLI definitely needs to pin its dependency versions (or bundle them) so that upstream releases can't silently break existing installs like this.