docs(scripts): document that prepare scripts run concurrently in workspaces #8823
+2
−0
Conversation
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
owlstronaut
approved these changes
Dec 3, 2025
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.
Description
This PR documents that prepare scripts run concurrently across workspace packages, addressing user confusion about execution order.
Changes
--foreground-scriptsworkaround for sequential executionFixes
Closes #4100
Context
Users with workspace setups that have interdependent packages (such as TypeScript projects where one package depends on another's build output) were confused when prepare scripts ran concurrently, causing build failures. The documentation implied sequential execution but didn't explicitly state that lifecycle scripts run concurrently.
Per @lukekarrys's comment in #4100, the action item was to document this behavior. The workaround is to use
--foreground-scripts(which can be set in.npmrcwithforeground-scripts=true) to force sequential execution, though this comes with performance trade-offs.