-
Notifications
You must be signed in to change notification settings - Fork 1.3k
chore: Lockfiles for all apps #8940
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
base: main
Are you sure you want to change the base?
Conversation
This reverts commit 5bff9d5.
|
||
starter: | ||
cd starters/docs && yarn --no-immutable && yarn tsc | ||
cd starters/docs && yarn --no-immutable && yarn up react-aria-components && yarn tsc |
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.
this forces the update from the version provided by the root workspace, to the latest tag on verdaccio. I'm not sure why there is no way to override this yarn behaviour and not look at the root workspace at all, but this appears to be the case currently. I think due to yarnpkg/yarn#4099
Build successful! 🎉 |
Build successful! 🎉 |
Closes
Split out from #8913
This just focuses on lock files and install states for all of our examples and starters. It's the first PR because it's probably the most important to establish. From here we can see what future changes are actually doing and something new can't come in and cause a different issue. Think of it as establishing a baseline.
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project: