-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
question(config): how to pin local packages to "workspace:*"? #189
Comments
It might be a pnpm issue. I wasn't successful with https://pnpm.io/package_json#dependenciesmetainjected but that's the closest I seem to get. Curious if anyone has run into this (fairly common) setup. |
This should be totally possible, happy to help but could you create a minimal repro? There are a few things I need to know to be better able to help you. Easiest way is to dupe your repo, delete everything but the package.json and syncpack config files, then anonymise anything you need to. Thanks. |
I'm getting the same problem; what essentially happens is that it works on first run, but that run updates every related local project's I had to write a script to clean-up after every run of |
@JamieMason Here is a small sample repo: https://github.com/Erid/syncpack-test If you run I'd appreciate your help! If there's anything that I can help with, let me know. |
I found the solution! In The initial problem I had is that it was working without any Anyway, I'm loving syncpack 🙂 |
You beat me to it @Erid, I was just writing a reply to you to say that 😆 Glad to hear it is sorted. I will leave this issue open until we learn how @kevinpruett-prime's project is configured. |
Thanks for this conversation. Let me see if this relates to my "issues". I'll post back 🙏 |
Yeah, looks like @Erid 's solution worked for me:
I'll mark this as closed. Thanks for the discussion 👍 |
Great, thanks to both of you 🥳 |
Actually, sorry to do this, but quick related question if you don't mind me reopening When I run
My semverGroup config is as follows:
Does this suggest that, for example, I need to set |
No problem. This was a recent bug, hopefully you are not on 12.1.0 and upgrading to that should fix it: #183 (comment). |
I'm on 12.3.0 |
Something sounds wrong there so I'll take a look. In the meantime, the easiest fix for now is to just set a version of eg. "0.0.0" |
Great, thanks @JamieMason 👍 |
I ran into this as well when following this example. I figured I could exclude In my setup, I'm using
I'm new to syncpack and just wanted to thank @JamieMason and the contributors for building such a useful tool for monorepos! 🙌 |
Great @imhoffd, yes omitting |
Which version of syncpack are you both using @imhoffd and @kevinpruett-prime? It should be a fixed bug actually that a package's .version should be read only. |
12.3.0 |
@JamieMason Yes, I'm on 12.3.0 as well. These
When I run Which does require these This is fixed with a |
Thanks @kevinpruett-prime that new issue would be handy, it'll be easier for other users to discover too. |
If I have a structure like the following:
I want to make sure
appA
andappB
always refer to the version of anypackages/*
withworkspace:*
I've tried the following
versionGroup
:But this just results in
LocalPackageMismatch
as it forces me to tag eachpackages/*
'spackage.json
with aversion: "workspace:*"
declaration. But when these set,pnpm
doesn't seem to work with theseversion
s and always throws.Is there an ideal setup for something like this?
The text was updated successfully, but these errors were encountered: