-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
separate lockfiles for example repos #3719
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The trpc deps become relative so itdoesn't fully work, unfortunately, leading the CI to fail.
Uurgh... theres prob an option we can add here similar to the lockfile setting, https://pnpm.io/npmrc#link-workspace-packages |
Slow doesn't really matter here (activating the cache took it down to 3 mins so not that slow anymore), it's a job only done when pushes to main - not a CI job people have to sit and wait for every push they make and wanna see if CI passes. What makes you think it won't work on future versions? tbh I'm a bit confused why it doesn't respect it just with the |
Closes #94
🎯 Changes
What changes are made in this PR? Is it a feature or a bug fix?
shared-workspace-lockfile=false
Tested here:
I guess the downside is that there will be a duplicate commit for the lockfile sync:

✅ Checklist