chore: migrate to pnpm #11248
Open
chore: migrate to pnpm #11248
+19,450
−22,658
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
refactor: removed .yarn folder fix: changed overrides approach feat: changed references
Replacing variables
Migrate scripts to pnpm and replaced yarn reference
Replaced yarn reference with pnpm
Added rule schema types
Fixed types
Launching app pnpm
Resolved problems with babel types
docs: updated comments to reflect pnpm usage instead of yarn
|
Great! In that case, if the issue is just that |
benmccann
reviewed
Jun 9, 2025
# Conflicts: # packages/eslint-plugin/package.json # packages/type-utils/package.json # yarn.lock
# Conflicts: # yarn.lock
# Conflicts: # package.json # packages/eslint-plugin/package.json # packages/type-utils/package.json # packages/website/package.json # yarn.lock
xaos7991
force-pushed
the
migrate-to-pnpm
branch
from
ebfcbff to
09b0f85
Compare
fix: resolved conflicts fix: corrected the version
xaos7991
force-pushed
the
migrate-to-pnpm
branch
from
09b0f85 to
5de32f8
Compare
# Conflicts: # CONTRIBUTORS.md # packages/eslint-plugin/package.json # packages/type-utils/package.json # tools/scripts/generate-contributors.mts # yarn.lock
# Conflicts: # packages/eslint-plugin/package.json # packages/type-utils/package.json # yarn.lock
# Conflicts: # knip.ts # nx.json # packages/ast-spec/package.json # packages/eslint-plugin-internal/package.json # packages/eslint-plugin/package.json # packages/integration-tests/package.json # packages/parser/package.json # packages/rule-schema-to-typescript-types/package.json # packages/rule-tester/package.json # packages/scope-manager/package.json # packages/type-utils/package.json # packages/types/package.json # packages/typescript-eslint/package.json # packages/typescript-estree/package.json # packages/utils/package.json # packages/visitor-keys/package.json # yarn.lock
|
Hi @JoshuaKGoldberg, @JamesHenry, @bradzacher, @kirkwaiblinger, and the rest of the team! 👋 First of all, thank you for all the work you do maintaining this project — it’s a huge help to the community, and I really appreciate the time and care you put into it. I was just wondering if there’s any chance a maintainer could take a look at this PR. I understand you're all busy, but since it hasn’t received a review from a maintainer yet, I’d be happy, along with @Jester175, to revise or adjust anything needed once there’s some feedback. Thanks again! |
# Conflicts: # tools/scripts/generate-sponsors.mts # yarn.lock
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Overview