-
-
Notifications
You must be signed in to change notification settings - Fork 696
refactor: migrate to pnpm workspace #2961
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
Conversation
⚠️ No Changeset found
Latest commit: 3cb4909
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
# Conflicts: # docs/.vitepress/theme/index.ts
# Conflicts: # docs/.vitepress/config.ts # eslint.config.mjs
FloEdelmann
commented
Dec 12, 2025
I'm a bit on the fence about this. This is an extra step for most contributors (which we can only expect to have plain npm installed), only to simplify the CJS/ESM-specific code in the docs repo.
We could probably use proper ESM syntax there, too, by switching to the .mts/.js file extension, can we?
And in the long term, we'll probably switch over to ESM for the whole repo anyway (and generate CJS in the build step, which you introduced in #2916).
Uh oh!
There was an error while loading. Please reload this page.
#2960 (comment)