-
Notifications
You must be signed in to change notification settings - Fork 148
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
feat: add pnpm as optional package manager #1020
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1020 +/- ##
==========================================
- Coverage 96.44% 96.32% -0.13%
==========================================
Files 28 28
Lines 2139 2177 +38
==========================================
+ Hits 2063 2097 +34
- Misses 76 80 +4
☔ View full report in Codecov by Sentry. |
Should I keep |
Let's keep it. It's a good way to test the new code paths.
A good first step before trying all environments is to start https://github.com/nodejs/citgm/actions/workflows/test-module.yml |
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.
LGTM but don't merge until we're sure pnpm
passes (or is skipped) on all supported platforms.
|
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 looks excellent. Thank you!
Well or we could add Next, that would also test the code paths. @Ethan-Arrowood what would the best commands be to build and test Next within CITGM? |
Not sure - I actually don't work on Next.js at all. But I will surface this with them. May not get a response until later as they are about to launch Next.js Conf and its all-hands-on-deck for that. |
I opened https://github.com/orgs/pnpm/discussions/7239 to ask the pnpm team about this. |
378b64f
to
18626bb
Compare
How exactly do you run these? I see “Run workflow,” what settings are you choosing? |
You can see the parameters logged here: https://github.com/nodejs/citgm/actions/runs/6612820965/job/18230215140 |
75d30f0
to
8ec479f
Compare
So like this? Why are there separate settings for CITGM branch and ref? Aren’t those the same thing? Anyway we seem to be making progress; it’s passing in some platforms/versions now: https://github.com/nodejs/citgm/actions/runs/6748209270 |
The first param (branch) should usually stay as |
Based on https://github.com/orgs/pnpm/discussions/7239#discussioncomment-7474442 it might take awhile before pnpm has a test suite that is consistently passing in CITGM. Perhaps I should remove the second commit from this PR, that adds pnpm to |
SGTM |
@targos I’ve dropped the |
This adds support for
pnpm
like we have for Yarn, resolving #1017. It also addspnpm
itself to the list of packages to test, though I don’t know if it will pass in all our environments. That’s the second commit and can be excluded if we want.