sui-bundler: exclude packages with script.dev#1975
Merged
Conversation
added 2 commits
March 26, 2026 21:19
428664b to
c857795
Compare
andresz1
approved these changes
Mar 26, 2026
jordevo
approved these changes
Mar 26, 2026
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
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.
Description
When using --link-package or --link-all, sui-bundler now automatically excludes packages that define a dev script in their
package.json. These packages are assumed to have their own file watcher/compiler running (e.g. tsup --watch, rollup -w), so linking them via sui-bundler would be redundant and could cause conflicts.A log message is printed to inform the user when a package is skipped for this reason.
README has been updated to document this behavior, including a note about using npm link directly for packages outside the monorepo.
Related Issue
N/A
Example
Given a monorepo with these packages:
To link my-lib during development, run its watcher separately:
If the package is not part of the monorepo, use
npm linkdirectly instead.