-
Notifications
You must be signed in to change notification settings - Fork 1
chore(deps-dev): Bump the npm group across 1 directory with 2 updates #100
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🔴 Bumping
typescriptto^7.0.2breakspnpm run lint: the already-installed@typescript-eslint/eslint-plugin@8.65.0throwstypescript-eslint does not support TS 7.0.at module load time whenever it detects a TS major version ≥ 7, aborting ESLint before any files are linted (exit code 2). Sincelintis invoked byprecommit:checkandall, this will also fail CI; the fix is to hold the typescript bump until typescript-eslint adds TS 7 support, or upgrade typescript-eslint to a version that supports it.Extended reasoning...
This PR bumps
typescriptfrom^6.0.3to^7.0.2(package.json:61) but leaves@typescript-eslint/eslint-pluginand@typescript-eslint/parserpinned at^8.64.0(resolving to8.65.0in the lockfile). That eslint-plugin version contains a hard guard at module load time indist/index.jsthat parsests.versionMajorMinorand does:This is distinct from (and stricter than) the soft warning in
@typescript-eslint/typescript-estree'swarnAboutTSVersion.js, which only warns for TS versions below its supported range. The eslint-plugin's own load-time guard throws unconditionally once it sees TS major version 7, regardless of how new/well-supported that version otherwise is.Code path:
package.json'slintscript (eslint src tests "scripts/**/*.ts") loads@typescript-eslint/eslint-plugin, which resolvestypescriptto whatever satisfies its peer dependency — now7.0.2per the updatedpnpm-lock.yaml. The guard fires during plugin initialization, before ESLint processes a single file, so the whole command aborts with exit code 2 and zero files linted.Why nothing else catches this first:
typecheckandtestare unaffected because they use@typescript/native(already pinned totypescript@^7.0.2prior to this PR) rather than thetypescriptpackage the eslint-plugin resolves against. So a green typecheck/test run gives no signal that lint is now broken.Step-by-step proof (empirically verified by three independent verifiers, all reproducing the same result):
typescriptresolves to7.0.2,@typescript-eslint/eslint-pluginresolves to8.65.0(...)(typescript@7.0.2).pnpm run lint(equivalentlynode node_modules/eslint/bin/eslint.js src tests "scripts/**/*.ts").typescript-eslint does not support TS 7.0.— confirmed to originate fromnode_modules/@typescript-eslint/eslint-plugin/dist/index.jslines ~43-50.precommit:checkrunspnpm run lint && pnpm run typecheck && ...andallrunspnpm run typecheck && pnpm run lint && ..., both of those composite scripts also fail, and CI (which presumably invokes one of these) will fail on this PR.Impact: Merging as-is breaks local
lint/precommit:check/alland will fail CI outright — a concrete, reproducible failure rather than a stylistic or descriptive mismatch.Fix options: hold the
typescriptdevDependency bump at^6.xuntil@typescript-eslintships TS 7 support, or bump@typescript-eslint/eslint-plugin/@typescript-eslint/parserto a version that supports TS 7.0 (if/when available) in the same PR.