-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
workflow: switch to pnpm #5060
workflow: switch to pnpm #5060
Conversation
scripts/release.js has a few uses of yarn. |
and on ci setup node action can also take care of pnpm cache now, https://github.com/sveltejs/vite-plugin-svelte/blob/36a087bd6b2cb303f13c6c91a3fae1decf26c5cc/.github/workflows/ci.yml#L31 |
Ugh, looks like we have the tests passing on every platform but Windows... that's going to be very hard to debug... |
Let me know if you need some help or if there are some issues with pnpm that I need to prioritize. |
|
||
- name: Build vite | ||
run: yarn ci-build-vite | ||
run: pnpm run ci-build-vite |
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.
you may actually keep the Yarn syntax here if you wish. run
is optional with pnpm as well.
Though you still have to escape options with --
like you did. We will probably make that work without --
in the future (pnpm/pnpm#3778)
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.
Yeah, I'm just doing it for consistency's sake
// pnpm treats file: protocols as link:, so it doesn't copy the actual files | ||
// into node_modules, causing Vite to still consider those deps linked. | ||
// This script is called from postinstall hooks in playground packages that | ||
// uses the file: protocol, and copies the file: deps into node_modules. |
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.
I think this issue is about a similar use case: pnpm/pnpm#3510
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.
It does sound similar. I also tried using .npmrc
inside a sub-package with package-import-method but it didn't seem to work.
I believe this is now ready. But let's hold off until tomorrow's team meeting.
Some notes on tests:
|
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.
If you don't want to rush this, please give me the chance to test this on my local machine(s).
currently I'm on mobile, will have time in about next 12h
Following was made on Arch Linux x86_64 5.10.68-1-lts Process for a newcomer/switcher to
|
2: why not Perf: benching build/test does not make much sense since most works are on the node side. Wondering what's the difference on deps installations? Side note: yarn v3 failed to distinguish the binaries as well: |
Co-authored-by: Shinigami <chrissi92@hotmail.de>
No description provided.