[BUG] ETARGET installing package I just published (not invalidating cache?)
Open
Nobody has claimed this yet.
Bug
Priority 2
Release 8.x
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
Publish libtap 1.3.0
cd to tap
try to install libtap@1.3.0
ETARGET forever, even though npm view libtap version reports 1.3.0
$ npm view libtap version
1.3.0
$ npm i libtap@1.3.0
npm ERR! code ETARGET
npm ERR! notarget No matching version found for libtap@1.3.0.
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/isaacs/.npm/_logs/2022-03-05T19_32_50_810Z-debug-0.log
$ npm -v
8.5.3
Expected Behavior
Should fetch version 1.3.0 from registry
Steps To Reproduce
See description
Environment
- npm: 8.5.3
- Node.js: v17.6.0
- OS Name: Darwin
- System Model Name: Darwin moxy.lan 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T6000 arm64
- npm config:
; "user" config from /Users/isaacs/.npmrc
@npm:registry = "https://npm.pkg.github.com/"
//npm.pkg.github.com/:_authToken = (protected)
//npm.toddself-pkg1.ghaedev.com/:_authToken = (protected)
//registry.internal.npmjs.com/:_authToken = (protected)
//registry.npm.red/:_authToken = (protected)
//registry.npmjs.org/:_authToken = (protected)
//registry.npmjs.rocks/:_authToken = (protected)
access = "public"
foo = "baz"
script-shell = "bash"
sign-git-commit = true
sign-git-tag = true
; node bin location = /usr/local/bin/node
; cwd = /Users/isaacs/.npm/_logs
; HOME = /Users/isaacs
; Run `npm config ls -l` to show all defaults.
Logs and relevant cache files attached below
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the publish-then-install sequence with npm 8.5.3, then inspect the attached debug log and _cacache archive for the registry metadata and cache behavior. Done means npm can install libtap@1.3.0 after it is published, while npm view continues to report the same version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100