Skip to content

ci: install @creative-int packages through the R2 npm cache - #5

Merged
lnittman merged 2 commits into
mainfrom
ci/npm-cache-20260928
Sep 29, 2026
Merged

lnittman merged 2 commits into
mainfrom
ci/npm-cache-20260928

Conversation

@lnittman

Copy link
Copy Markdown
Contributor

Installs @creative-int packages through config's npm-cache Worker, a pull-through cache in R2 (config machine/README.md § npm package cache in R2). GitHub Packages data transfer is the org's only paid GitHub line: 17.4 GB in August, 35 GB ($12.50) in September. After this, each tarball leaves GitHub once.

  • .npmrc: the @creative-int registry is https://npm-cache.luke-nittmann.workers.dev, and the cache host gets the same ${NPM_TOKEN}. The npm.pkg.github.com auth line stays, for the way back.
  • pnpm-lock.yaml: the 8 pinned tarball URLs point at the cache. Integrity hashes are unchanged, so pnpm still verifies every byte.

Access stays GitHub's: the Worker holds no credential, and it serves a tarball only after GitHub has accepted the caller's own token for that package. This PR's CI install (and a Vercel preview, where there is one) is the proof.

🤖 Generated with Claude Code

lnittman and others added 2 commits September 28, 2026 20:33
GitHub Packages data transfer is the org's only paid GitHub line ($12.50 in September). The npm-cache Worker keeps each tarball in R2 after its first download; access stays GitHub's (callers send the same NPM_TOKEN).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub Packages data transfer is the org's only paid GitHub line ($12.50 in September). The npm-cache Worker keeps each tarball in R2 after its first download; access stays GitHub's (callers send the same NPM_TOKEN).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lnittman
lnittman merged commit f374ade into main Sep 29, 2026
2 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.

1 participant