feat: install pixelteer from prebuilt release tarball - #764
Merged
Conversation
Switch pixelteer from a git dependency (which runs its tsc prepare at install time and needs a fragile commit-pinned onlyBuiltDependencies entry under pnpm 10) to the prebuilt release-asset tarball. With expost already prebuilt, the onlyBuiltDependencies allowlist is now empty and removed entirely. Blocked on: pinepeakdigital/pixelteer cutting the v1.0.0 release. Lockfile regen + verification happen once that asset exists. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
narthur
marked this pull request as ready for review
July 15, 2026 14:13
Locks pixelteer to the v1.0.0 release asset (stable URL + integrity) now that the release exists. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dreeves
temporarily deployed
to
feat/pixelteer-from-release - beeblog PR #764
July 15, 2026 14:17 — with 
Render
Destroyed
Render
Destroyed
Contributor
Build Performance⚡ -0.03s (-0.6%) average build time
|
Contributor
Accessibility IssuesSummaryNo baseline issues found.
Issue Breakdown
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
pixelteerdependency at the prebuilt release-asset tarball (v1.0.0) instead of the git ref (github:pinepeakdigital/pixelteer).onlyBuiltDependenciesallowlist entirely — with expost (feat: install expost from prebuilt release tarball #762) and now pixelteer both prebuilt, nothing is left needing install-time build approval.Why
Same fix as expost (#762). As a git dependency, pixelteer runs its
prepare(tsc+ copyinject.css) at install time, which under pnpm ≥10 needs a fragile commit-pinnedonlyBuiltDependenciesentry and breaks cold installs. The release tarball ships builtdist/, so consumers never run the build, and the allowlist is gone.puppeteeris a peerDependency of pixelteer that blog provides directly, so this doesn't affect puppeteer's Chromium install.Depended on PinePeakDigital/pixelteer#18 (merged), which auto-published pixelteer
v1.0.0withpixelteer-1.0.0.tgz. The lockfile pins that asset by stable URL + integrity (via the pnpm@10.34.5 on master), so frozen installs stay reproducible.This completes the expost + pixelteer prebuild work and closes out #656.