-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
chore: yarn to pnpm #334
chore: yarn to pnpm #334
Conversation
🦋 Changeset detectedLatest commit: 9e2d388 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 |
Pull Request Test Coverage Report for Build 4971008653Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
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 took a diff for lib dir between main branch and this branch, and only difference is the comment which is the word yarn and pnpm.
@@ -69,6 +69,7 @@ module.exports = { | |||
"@typescript-eslint/no-use-before-define": "off", | |||
"@typescript-eslint/no-explicit-any": "off", | |||
"no-implicit-globals": "off", | |||
"no-void": ["error", { allowAsStatement: true }], |
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'm not sure why suddenly ESLint error occurs but I needed to add this.
test: | ||
runs-on: ubuntu-latest | ||
strategy: | ||
matrix: | ||
node-version: [12.x, 14.x, 16.x, 17.x, 18.x, 19.x] | ||
node-version: [14.x, 16.x, 17.x, 18.x, 19.x] |
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 dropped Node 12 because pnpm 7 doesn't support it.
Can we do this?
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.
How about creating a test-for-node12
job and using pnpm v6?
test-for-node12:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: pnpm/action-setup@v2
with:
version: 6.35.1
If it still doesn't work, let's drop support for node v12.
Since this package is still at 0.x, I believe it can contain breaking changes in minor versions.
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.
Thank you for this PR!
@@ -28,12 +28,12 @@ jobs: | |||
- uses: actions/setup-node@v3 |
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 pnpm/action-setup
is necessary.
- uses: actions/setup-node@v3 | |
- uses: pnpm/action-setup@v2 | |
- uses: actions/setup-node@v3 |
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 couldn't do this perfectly😇
fixed!
92a644b
test: | ||
runs-on: ubuntu-latest | ||
strategy: | ||
matrix: | ||
node-version: [12.x, 14.x, 16.x, 17.x, 18.x, 19.x] | ||
node-version: [14.x, 16.x, 17.x, 18.x, 19.x] |
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.
How about creating a test-for-node12
job and using pnpm v6?
test-for-node12:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: pnpm/action-setup@v2
with:
version: 6.35.1
If it still doesn't work, let's drop support for node v12.
Since this package is still at 0.x, I believe it can contain breaking changes in minor versions.
@@ -27,16 +27,16 @@ jobs: | |||
node-version: 16 | |||
|
|||
- name: Install Dependencies | |||
run: yarn | |||
run: pnpm install |
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 pnpm/action-setup
is necessary.
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 couldn't do this perfectly😇
fixed!
92a644b
f9abea9
to
3702dcc
Compare
Hmm. It seems that v6 and v7 handle command line arguments differently. https://raulmelo.dev/en/blog/migrating-from-pnpm-6-to-7#running-a-script |
Let's drop support for Node v12 😄 |
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.
Thank you very much!
close: #333