-
Notifications
You must be signed in to change notification settings - Fork 44
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
Improve compile package detection in PNPM apps #840
Conversation
🦋 Changeset detectedLatest commit: 78b90ab The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Nice work cracking that nut!
Tested in an app and metropolis ✅ |
This PR enables sku to detect compile packages inside the PNPM virtual store (
node_modules/.pnpm
). The current implementation of compile package detection only finds@seek
scoped packages at the root ofnode_modules
, so if you're not using PNPM withnode-linker=hoisted
, then sku can't find compile packages that are transitive dependencies (i.e. inside the PNPM virtual store).Was also seeing some flakiness in the
lint-format
test snapshots where sometimes jest was reporting that the snapshots failed with diffs that looked identical except for the text colours. This lead me to try stripping ANSI escape codes in the snapshot serializer, and this seems to have worked AFAICT.The storybook tests also decided to be flakey today, so I've increased the timeout on one of the queries we do and that seems to have helped.