Skip to content

Bundle CLI to eliminate dependency conflicts#134

Open
marcospassos wants to merge 1 commit intomasterfrom
change-bundle
Open

Bundle CLI to eliminate dependency conflicts#134
marcospassos wants to merge 1 commit intomasterfrom
change-bundle

Conversation

@marcospassos
Copy link
Copy Markdown
Member

@marcospassos marcospassos commented May 5, 2026

Summary

The CLI was published with all runtime dependencies externalized, so installing it pulled ~50 transitive packages into the host project's node_modules and caused frequent version conflicts (notably around Babel and Zod).

This PR ships the CLI as a single self-contained bundle. Consumers now install one package with zero transitive dependencies.

Bundle size

Step Size
Before (deps externalized) 420 KB shim + ~50 transitive packages
Bundled, all deps inlined 2.86 MB
+ emoji regex / esprima / browserslist stubs 2.31 MB

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

@marcospassos marcospassos requested a review from a team as a code owner May 5, 2026 18:23
@marcospassos marcospassos added the maintenance Housekeeping label May 5, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 5, 2026

👋 @marcospassos
Thanks for your contribution!
The approval and merge process is almost fully automated 🧙
Here's how it works:

  1. You open a new pull request
  2. Automated tests check the code
  3. Maintainers review the code
  4. Once approved, the PR is ready to merge.

👉 Omit the extended description
Please remove the commit body before merging the pull request.
Instead, include the pull request number in the title to provide the full context
about the change.

☝️ Lastly, the title for the commit will come from the pull request title. So please provide a descriptive title that summarizes the changes in 50 characters or less using the imperative mood.
Happy coding! 🎉

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 5, 2026

Open in StackBlitz

npm i https://pkg.pr.new/croct@134

commit: 28150b0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Housekeeping

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants