Commitlint: CLI package installation fails with `npm` and Artifactory

[chris-dura]

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

• [x] 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)

1. 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 |

[chris-dura]

Looks like there was an upstream problem with the NPM registry and Artifactory.

[chris-dura]

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 🤷‍♀️

[byCedric]

Keep us posted if you think something is wrong!

The only part I can contribute is that @commitlint/[email protected] seems to be available at the NPM website itself. So the no-matching-versions doesn't seems to be valid, right? Are you using a mirror or other registry maybe?

[escapedcat]

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 :)

[chris-dura]

The only part I can contribute is that @commitlint/[email protected] seems to be available at the NPM website itself.

@byCedric -- Yeah, so when we install new packages, our Artifactory is supposed to cache those updates from the public registry to our Artifactory. Then the _next_ person to install the package will grab the one from Artifactory. However, in the case of @commitlint/[email protected]... our Artifactory is refusing to cache it (for some reason), so when some one tries to install, Artifactory throws "no matching version"... even though there IS one on the public registry.

It's very annoying but I do think this is not related to something commitlint does.

Yeah, I'm feeling this as well.