Mark packages as side-effect free for tree shaking#357
Merged
Conversation
Adds "sideEffects": false to each published package so bundlers like Rollup can drop unused imports. orm-cli lists ./build/cli.js as its sole side-effectful module since the CLI entrypoint runs on import. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Coverage Report
|
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
1 participant
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
"sideEffects": falseto all 9 packages underpackages/so bundlers like Rollup can tree-shake unused imports.orm-cliinstead lists./build/cli.jsas its sole side-effectful file, since the CLI entrypoint runs on import; everything reachable from itsexports(./build/index.js) remains tree-shakable.Test plan
@casekit/ormproduces a smaller bundle than before🤖 Generated with Claude Code