Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CLI package installation fails with `npm` and Artifactory

See original GitHub issue

Running npm install @commitlint/cli fails.

Expected Behavior

That it doesn’t fail.

Current Behavior

npm install @commitlint/cli

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @commitlint/rules@^7.3.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.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@commitlint/lint'
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/CDura/.npm/_logs/2019-01-17T23_34_20_182Z-debug.log

Affected packages

cli
core
prompt
config-angular

Possible Solution

Looks like some one of the cli package’s dependencies is attempting to install @commitlint/rules@^7.3.1 which doesn’t exist.

Steps to Reproduce (for bugs)

Run npm install @commitlint/cli

Context

My CI builds are failing as well, because I use a caret "@commitlint/cli": "^7.2.1".

Your Environment

Executable	Version
`commitlint --version`	^7.2.1
`git --version`	git version 2.19.2
`node --version`	v10.15.0

Issue Analytics

State:
Created 5 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

3reactions

escapedcatcommented, Jan 20, 2019

We had this issue before and eventually it started to work again. Not neccessarily because of this article by jfrog but maybe because we cleared caches and restarted and updated Artifcatory.

commitlint isn’t the only package which provoked this issue though. Unfortunately we still do not have a good working solution on how to avoid this in the future.
We contacted jfrog but so far there isn’t much we can do. It’s very annoying but I do think this is not related to somethign commitlint does.

But happy to get more input from others if the stumble across this issue here 😃

1reaction

chris-duracommented, Jan 18, 2019

All other NPM packages (normal and scoped) work fine.

I’ll do more testing tomorrow and try and figure out if it’s something wrong with the published version of this package in particular. Perhaps something went wrong or got corrupted in the public publish process that is causing our private Artifactory instance to 🤢… at which point it might be appropriate to re-open this 🤷‍♀️