Conversation
📝 WalkthroughWalkthroughUpdated devDependencies in package.json: lint-staged bumped from 16.2.3 to 16.4.0, and TypeScript bumped from ~5.8.0 to ~5.9.0. Both are development-only dependency version updates; no exported API or runtime behavioral changes included. Sequence Diagram(s)Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
package.json
🔇 Additional comments (2)
package.json (2)
89-89: PR description claims 4 updates; diff shows 2.PR objectives mention prettier 3.6.2→3.7.4 and yjs 13.6.27→13.6.28, but these lines show no changes.
Also applies to: 92-92, 101-102
89-89: lint-staged 16.2.7 is safe to use.Version published November 19, 2025 with a minor fix for error message handling when tasks fail. No issues identified.
|
47f630b to
f49ded8
Compare
|
a396815 to
031aa51
Compare
031aa51 to
0e5c11d
Compare
0e5c11d to
2a097f4
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 101: package.json currently pins "typescript": "~5.9.0" but the
`@typescript-eslint` packages need bumping; update the dependency entries for
"@typescript-eslint/parser" and "@typescript-eslint/eslint-plugin" to ">=6.5.0"
(e.g., "6.5.0" or a compatible caret range) in package.json, then run your
package manager install (npm/yarn/pnpm) to refresh node_modules and the lockfile
so the parser and plugin match TypeScript 5.9; ensure any ESLint config
references (parser in .eslintrc or eslint config) remain pointed to
"@typescript-eslint/parser".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| "stylelint-csstree-validator": "^3.0.0", | ||
| "stylelint-prettier": "^4.0.0", | ||
| "typescript": "~5.8.0", | ||
| "typescript": "~5.9.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What TypeScript versions are officially supported by @typescript-eslint/parser6.1.0 and@typescript-eslint/eslint-plugin 6.1.0? Does that support include TypeScript 5.9.x?
💡 Result:
For @typescript-eslint/parser 6.1.0 (and therefore @typescript-eslint/eslint-plugin 6.1.0, which relies on the parser), the project’s “officially supported TypeScript versions” range for that v6 line is:
- TypeScript
>=3.3.1 <5.2.0(this is the range emitted in the tool’s own “SUPPORTED TYPESCRIPT VERSIONS” warning output for v6-era installs). [1] - Shortly after, in @typescript-eslint/parser 6.5.0, they bumped support to TypeScript 5.2, implying versions before 6.5.0 (including 6.1.0) did not include 5.2+. [2]
So: No—TypeScript 5.9.x is not included in the official support for 6.1.0 (it’s far above the <5.2.0 ceiling). [1]
Sources:
[1] GitHub (eslint/eslint) issue showing the parser’s warning output with “SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <5.2.0” eslint/eslint#18825
[2] NewReleases entry for @typescript-eslint/parser 6.5.0 noting “bump supported TS version to 5.2” https://newreleases.io/project/npm/%40typescript-eslint/parser/release/6.5.0
Upgrade @typescript-eslint to ≥6.5.0 for TypeScript 5.9 support.
TypeScript 5.9.0 exceeds the supported range for @typescript-eslint 6.1.0 (which caps at <5.2.0). Support for TypeScript 5.2+ was added in @typescript-eslint/parser 6.5.0. Update both @typescript-eslint/parser and @typescript-eslint/eslint-plugin to 6.5.0 or later.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 101, package.json currently pins "typescript": "~5.9.0"
but the `@typescript-eslint` packages need bumping; update the dependency entries
for "@typescript-eslint/parser" and "@typescript-eslint/eslint-plugin" to
">=6.5.0" (e.g., "6.5.0" or a compatible caret range) in package.json, then run
your package manager install (npm/yarn/pnpm) to refresh node_modules and the
lockfile so the parser and plugin match TypeScript 5.9; ensure any ESLint config
references (parser in .eslintrc or eslint config) remain pointed to
"@typescript-eslint/parser".
This PR contains the following updates:
5.5.4→5.5.516.2.3→16.4.03.6.2→3.8.13.0.0→3.1.0~5.8.0→~5.9.013.6.27→13.6.30Release Notes
prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.5.5Compare Source
Patch Changes
#772
7264ed0Thanks @BPScott! - Bump prettier-linter-helpers dependency to v1.0.1#776
77651a3Thanks @aswils! - fix: bump synckit for yarn PnP ESM issuelint-staged/lint-staged (lint-staged)
v16.4.0Compare Source
Minor Changes
687fc90Thanks @hyperz111! - Replacemicromatchwithpicomatchto reduce dependencies.v16.3.4Compare Source
Patch Changes
9d6e827Thanks @iiroj! - Update dependencies, includingtinyexec@1.0.4to make sure localnode_modules/.binare preferred to global locations (released intinyexec@1.0.3).v16.3.3Compare Source
Patch Changes
0109e8dThanks @iiroj! - Make sure Git's warning about CRLF line-endings doesn't interfere with creating initial backup stash.v16.3.2Compare Source
Patch Changes
2adaf6cThanks @iiroj! - Hide the extracmdwindow on Windows by spawning tasks without thedetachedoption.v16.3.1Compare Source
Patch Changes
cd5d762Thanks @iiroj! - Removenano-spawnas a dependency frompackage.jsonas it was replaced withtinyexecand is no longer used.v16.3.0Compare Source
Minor Changes
#1698
feda37aThanks @iiroj! - Run external processes withtinyexecinstead ofnano-spawn.nano-spawnreplacedexecain lint-staged version 16 to limit the amount of npm dependencies required, but caused some unknown issues related to spawning tasks. Let's hopetinyexecimproves the situation.#1699
1346d16Thanks @iiroj! - Removepidtreeas a dependency. When a task fails, its sub-processes are killed more efficiently via the process group on Unix systems, and thetaskkillcommand on Windows.Patch Changes
87467aaThanks @iiroj! - Incorrect brace expansions like*.{js}(nothing to expand) are detected exhaustively, instead of just a single pass.v16.2.7Compare Source
Patch Changes
ef74c8dThanks @iiroj! - Do not display a "failed to spawn" error message when a task fails normally. This message is reserved for when the task didn't run because spawning it failed.v16.2.6Compare Source
Patch Changes
33d4502Thanks @Adrian-Baran-GY! - Fix problems with--continue-on-erroroption, where tasks might have still been killed (SIGINT) when one of them failed.v16.2.5Compare Source
Patch Changes
9e02d9dThanks @iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.v16.2.4Compare Source
Patch Changes
#1682
0176038Thanks @iiroj! - Update dependencies, includingnano-spawn@2.0.0with bug fixes.#1671
581a54eThanks @iiroj! - Speed up execution by only importing theyamldepedency if using YAML configuration files.prettier/prettier (prettier)
v3.8.1Compare Source
v3.8.0Compare Source
diff
🔗 Release note
v3.7.4Compare Source
diff
LWC: Avoid quote around interpolations (#18383 by @kovsu)
TypeScript: Fix comment inside union type gets duplicated (#18393 by @fisker)
TypeScript: Fix unstable comment print in union type comments (#18395 by @fisker)
v3.7.3Compare Source
diff
API: Fix
prettier.getFileInfo()change that breaks VSCode extension (#18375 by @fisker)An internal refactor accidentally broke the VSCode extension plugin loading.
v3.7.2Compare Source
diff
JavaScript: Fix string print when switching quotes (#18351 by @fisker)
JavaScript: Preserve quote for embedded HTML attribute values (#18352 by @kovsu)
TypeScript: Fix comment in empty type literal (#18364 by @fisker)
v3.7.1Compare Source
diff
API: Fix performance regression in doc printer (#18342 by @fisker)
Prettier 3.7.1 can be very slow when formatting big files, the regression has been fixed.
v3.7.0Compare Source
diff
🔗 Release Notes
csstree/stylelint-validator (stylelint-csstree-validator)
v3.1.0Compare Source
css-treeto^3.2.1microsoft/TypeScript (typescript)
v5.9.3: TypeScript 5.9.3Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement
Downloads are available on:
v5.9.2: TypeScript 5.9Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement
Downloads are available on:
yjs/yjs (yjs)
v13.6.30Compare Source
05049395d5f1adv13.6.29Compare Source
cff7de1v13.6.28Compare Source
ed29b644120d72783a7c4f94f2ebd5a74c9f4fa053b3c92f60b8a0fcc87430a61258d8fcfdba12995fcdbc941a5731031455df734273c53b2d09ed44ea9a75Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.