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
Bundle tar-stream's Node.js dependency path so consumers no longer install tar-stream and its transitive packages. Archive extraction behavior stays unchanged.
The clean npm comparison removes 12 runtime packages and saves about 5.7 MB net with current registry resolutions. Bundled JavaScript grows by 38,050 bytes; bundling excludes the unused Bare runtime packages. The independent review found no actionable issues and confirmed this tradeoff uses the existing build mechanism without replacing archive functionality.
Scope: three build/dependency metadata files. No dependency versions, runtime source, docs, or skills changed.
Validation
Validated content at de64381d7be8bef93031a856cf8454183c19ffe4:
Repo Guards is correctly blocking this head: moving root tar-stream to devDependencies leaves packages/host-kit/package.json declaring it as a runtime dependency, so R11 can no longer match the private package’s external dependency to a root published dependency.
Move tar-stream to host-kit’s devDependencies too, following the existing bundled-dependency pattern, keep the root entry only for build resolution, and rerun Repo Guards plus the packed clean-install/archive checks. Do not weaken R11 or restore the root runtime dependency, which would defeat the install-footprint goal. The established tsdown bundling path and the reported +37.3 kB packed-output tradeoff otherwise look sound.
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
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.
Summary
Bundle tar-stream's Node.js dependency path so consumers no longer install tar-stream and its transitive packages. Archive extraction behavior stays unchanged.
The clean npm comparison removes 12 runtime packages and saves about 5.7 MB net with current registry resolutions. Bundled JavaScript grows by 38,050 bytes; bundling excludes the unused Bare runtime packages. The independent review found no actionable issues and confirmed this tradeoff uses the existing build mechanism without replacing archive functionality.
Scope: three build/dependency metadata files. No dependency versions, runtime source, docs, or skills changed.
Validation
Validated content at
de64381d7be8bef93031a856cf8454183c19ffe4:The full affected-check run was canceled before starting at the user's request. CI on this head remains pending.