Replies: 1 comment 4 replies
-
What use case does this solve for? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Goals
NPM workspaces allows the root package to be a published package.
This root package can be a dependency of another workspace so it can trigger the originating
build
script again.There should be a feature that prevents getting in an endless loop calling the originating build script over and over.
This is an example of such a use case https://github.com/muxinc/player.style/blob/main/package.json#L26
Non-goals
No response
Background
Alternatives are checking an env var in the NPM script or
removing the NPM scripts in the root workspace and use the turbo CLI directly or
use different NPM script naming but this is easily messed up and cumbersome.
Proposal
Internally it could be quite simple of checking an environment variable or if the next script is the same script as the original script.
Beta Was this translation helpful? Give feedback.
All reactions