What I Wanted to Do
1.0.2 of the
errlop package after the CLI said the publish happened successfully.
What Happened Instead
$ eval "$(curl -fsSL https://raw.githubusercontent.com/bevry/awesome-travis/a16fffacc146944edb58d02bbc565bf467099b18/scripts/node-publish.bash)" running on node version v8.11.3 which IS the desired v8.11.3 releasing to npm... creating npmrc with auth token... publishing... + firstname.lastname@example.org ...released to npm
npm publish --access public behind the scenes.
Go to consume version
1.0.2 which the logs above state was successfully published:
> npm i email@example.com npm ERR! code ETARGET npm ERR! notarget No matching version found for firstname.lastname@example.org 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! A complete log of this run can be found in: npm ERR! /Users/balupton/.cache/npm/_logs/2018-07-27T08_42_51_656Z-debug.log
Check again while I’m posting this issue:
This has happened to me only twice over the past 2 weeks. Unsure what the conditions are for it.
Searching online these two resources popped up:
- Missing package versions after apparently successful publishes
How long of a delay should we expect? What circumstances for the delay are there?