The idea is to create ad-hoc workspaces for the subset of the packages you are working on, and thus obviate the need to publish packages while working, and defer the "real" bilt process till the end (or to CI).
SOmething like a new command bilt-workspace which looks at which packages were changed and create a workspace for just those packages (and npm install-s them). Obviously, just like the bilt CLI does., the command should also accept the packages to develop on, and not just let Bilt infer them from the changed packages.
The idea is to create ad-hoc workspaces for the subset of the packages you are working on, and thus obviate the need to publish packages while working, and defer the "real" bilt process till the end (or to CI).
SOmething like a new command
bilt-workspacewhich looks at which packages were changed and create a workspace for just those packages (andnpm install-s them). Obviously, just like thebiltCLI does., the command should also accept the packages to develop on, and not just let Bilt infer them from the changed packages.