Skip to content
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

Error installing @datadog/datadog-ci #1493

Closed
victorwhy opened this issue Nov 14, 2024 · 2 comments
Closed

Error installing @datadog/datadog-ci #1493

victorwhy opened this issue Nov 14, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@victorwhy
Copy link

victorwhy commented Nov 14, 2024

Bug description

Hi,

I'm on node version 20.12 (as is our build pipeline), and running this command:

npm install -g @datadog/datadog-ci

results in this error:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @smithy/node-config-provider@^3.1.10.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

Describe what you expected

That datadog-ci is installed without failling.

Steps to reproduce the issue

On node version 20.12, run npm install -g @datadog/datadog-ci

Additional context

  • MacOS 14.2.1 (23C71)
  • Node: 20.12.0
  • npm 10.5.0

Looks like this was updated very recently, so maybe thats why? but wondering why this is pointing at a version that's not fully available yet?

https://www.npmjs.com/package/@smithy/node-config-provider

Command

None

@victorwhy victorwhy added the bug Something isn't working label Nov 14, 2024
@Drarig29
Copy link
Contributor

Hi @victorwhy!

You should report this to AWS, this is likely an issue with their upgrading system: a dependant package was probably published before its dependency. Does it work now?

@victorwhy
Copy link
Author

Hi @victorwhy!

You should report this to AWS, this is likely an issue with their upgrading system: a dependant package was probably published before its dependency. Does it work now?

yeah! it resolved itself - 100% what you described, although it was only happening when installing this dependency

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants