You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
npm install fails on a fresh clone: lockfile pins nuxt-component-meta to a dead pkg.pr.new URL #2
A fresh clone cannot be installed. npm install / npm ci fails with E404 because package-lock.json pins the transitive dependency nuxt-component-meta (pulled in by @nuxt/content) to a pkg.pr.new preview URL that no longer resolves:
npm error 404 Not Found - GET https://pkg.pr.new/nuxt-component-meta@e3eb2c4
npm error 'nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4' is not in this registry.
curl -s -o /dev/null -w "%{http_code}" https://pkg.pr.new/nuxt-component-meta@e3eb2c4 returns 404. This blocks every new contributor from running the app or tests.
What to do
Regenerate the lockfile so nuxt-component-meta resolves from the public npm registry (e.g. bump @nuxt/content to a release whose lock entry is a normal registry tarball, or add an explicit nuxt-component-meta devDependency and re-run npm install).
Remove the dead pkg.pr.new pin from package-lock.json.
Verify both npm ci and rm -rf node_modules package-lock.json && npm install succeed from clean.
Acceptance criteria
npm ci completes from a clean clone with no 404.
grep -c "pkg.pr.new" package-lock.json returns 0.
npm run dev and npm run test still work.
Getting started (files)
package-lock.json — the resolution at lines ~1877 and the package block at ~13068.
Fixed in #19 — the lockfile entry for nuxt-component-meta now resolves from the npm registry instead of the dead pkg.pr.new URL. Verified npm ci succeeds from a clean clone and grep -c "pkg.pr.new" package-lock.json returns 0. This issue will close automatically when #19 is merged.
Activity
marvelefe commentedon Oct 17, 2026
Fixed in #19 — the lockfile entry for
nuxt-component-metanow resolves from the npm registry instead of the deadpkg.pr.newURL. Verifiednpm cisucceeds from a clean clone andgrep -c "pkg.pr.new" package-lock.jsonreturns 0. This issue will close automatically when #19 is merged.