-
Notifications
You must be signed in to change notification settings - Fork 11
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
Use corepack pnpm instead of volta npm #109
Conversation
✅ Deploy Preview for nebula-docs-dn ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Looks like we need to add |
package.json
Outdated
"volta": { | ||
"node": "18.16.0", | ||
"npm": "8.17.0" | ||
"node": ">=20.9.0" |
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.
Let's leave this a bit more loose. No reason not to allow node 18+, is there?
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.
done
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.
Hm, I think this got lost in a rebase.
d300857
to
2dcc4ad
Compare
I can't replicate this locally 🫠 |
I can. Maybe try clearing your typescript cache? |
This looks like a much bigger PR than just moving from volta to pnpm. Let's tone it down a bit, and maybe just use regular npm if pnpm is giving us problems. The main goal is to unblock John. |
only issue is that corepack doesn't support npm, so looks like John's commit on his own PR is the right way to go then |
Alright, then let's get his PR in, then scope this down to just migrating to pnpm? |
b02139d
to
af131ee
Compare
reset to "just pnpm" |
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 pushed a commit to fix the tsc errors.
@@ -18,15 +18,18 @@ | |||
"@docusaurus/preset-classic": "2.3.0", | |||
"@mdx-js/react": "^1.6.22", | |||
"clsx": "^1.2.1", | |||
"parse-domain": "^7.0.1", |
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.
why downgrade parse-domain?
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.
The last version that wasn't esm-only.
This updates our node/package manager situation to depend on pnpm and corepack, similar to webclient/www
88b4d7e
to
921f912
Compare
rebased |
|
||
# macOS-specific files | ||
.DS_Store | ||
tsconfig.tsbuildinfo |
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.
Why did we need to add a prettierignore when moving from npm to pnpm?
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.
b/c it started formatting pnpm-lock.json
package.json
Outdated
"volta": { | ||
"node": "18.16.0", | ||
"npm": "8.17.0" | ||
"node": ">=20.9.0" |
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.
Hm, I think this got lost in a rebase.
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.
Readme suggestion, but otherwise looks good.
README.md
Outdated
|
||
To install our javascript dependencies, run `pnpm install` (or `pnpm i` for short). You'll want to do this whenever you | ||
change branches, if there's a possibility that dependencies have been changed or updated. If you're not able to start up | ||
the client app, this is a good first troubleshooting step to take. To get `pnpm`, run `corepack enable` after installing `node`, and `corepack` should install the right `pnpm` version for you. |
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'd recommend moving this up higher, for those who are following along step-by-step.
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.
done
This updates our node/package manager situation to depend on pnpm and corepack, similar to webclient/www