-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude Satellite from pnpm workspace #3228
Conversation
I updated the description. |
I thought we didn't want the services to use local Satellite though |
@rclee91, my bad, I updated the description again, s/do/do not/ |
In this case, do we still use |
I guess we're giving Satellite the same treatment as our React Native app so they're both living in the same repository as the rest of the services but they functioning like introverted roommates that don't explicitly communicate with the other services unless we want them to by doing this? <path/to/service>/package.json
|
yes |
Wait, I'm wrong. |
Sorry, have you tried deleting all the |
We probably have to do the same thing we do with React Native with
|
Yes, probably, either we have to figure out how to link Satellite or do that. |
This is probably a bug in pnpm pnpm/pnpm#3561 |
Is this something that is still needed, even after the merge of #3247 ? |
@rclee91 we don't need this anymore. I'm gonna close it. |
Exclude Satellite from pnpm workspaces.
I think we misunderstood the purpose of
pnpm-workspace.yaml
. The file exists to tell pnpm to link packages from the workspace if the available packages match the declared ranges.So if we do not want to use the local Satellite, for example, we should not list it in
pnpm-worksapce
.Better fix of #3191