Skip to content

Conversation

snowystinger
Copy link
Member

@snowystinger snowystinger commented Sep 29, 2025

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:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:


starter:
cd starters/docs && yarn --no-immutable && yarn tsc
cd starters/docs && yarn --no-immutable && yarn up react-aria-components && yarn tsc
Copy link
Member Author

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

@rspbot
Copy link

rspbot commented Sep 29, 2025

@rspbot
Copy link

rspbot commented Sep 29, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants