Skip to content

skills(api-recon): point the lockfile at the public npm registry - #420

Merged
BaaRai merged 1 commit into
BaaRai:mainfrom
ldevbr:contrib/api-recon-npm-registry
Nov 20, 2026
Merged

BaaRai merged 1 commit into
BaaRai:mainfrom
ldevbr:contrib/api-recon-npm-registry

Conversation

@ldevbr

@ldevbr ldevbr commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Every resolved URL in skills/api-recon/scripts/package-lock.json pointed at registry.npmmirror.com (a third-party mirror). Repoint them to registry.npmjs.org. The integrity hashes are unchanged and still valid, so the tarballs are byte-identical; npm ci --registry=https://registry.npmjs.org installs cleanly and puppeteer-core loads.

Every `resolved` URL in skills/api-recon/scripts/package-lock.json pointed at
registry.npmmirror.com (a third-party mirror). Repoint them to
registry.npmjs.org. The integrity hashes are unchanged and still valid, so the
tarballs are byte-identical; `npm ci --registry=https://registry.npmjs.org`
installs cleanly and puppeteer-core loads.
@BaaRai
BaaRai merged commit 0ffb0a6 into BaaRai:main Nov 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants