Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@
"@semantic-release/npm": "^13.0.0",
"@semantic-release/release-notes-generator": "^14.1.0",
"semantic-release": "^25.0.1",
"typescript": "^5.5.4",
"typescript": "^5.9.3",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Confirm TS 5.9 upgrade doesn’t surface new type errors.

TypeScript 5.9 tightens type argument inference and adjusts DOM/lib typings (for example, ArrayBuffer no longer covers Node Buffer), so code that passed under 5.5.4 may now fail to type-check. Please rerun the full TypeScript lint pipeline and address any regressions before merging; if you encounter new Buffer/ArrayBuffer errors, update @types/node to the latest compatible release. (visualstudiomagazine.com)


🏁 Script executed:

#!/bin/bash
npm install
npm run lint:ts

Length of output: 2059


Update @types/node to resolve TS 5.9 Buffer typing errors.

The upgrade to TypeScript 5.9 exposes mismatches in @types/node Buffer declarations (errors in buffer.d.ts and fs/promises.d.ts). Install the latest compatible Node types (e.g. npm install -D @types/node@latest), then rerun npm run lint:ts until tsc --noEmit passes.

🤖 Prompt for AI Agents
In package.json around line 42, TypeScript 5.9 exposes type mismatches with the
currently installed @types/node; update the Node type definitions to a version
compatible with TS 5.9 by installing the latest @types/node as a dev dependency
(e.g. run npm install -D @types/node@latest or update devDependencies entry),
then rerun npm run lint:ts and tsc --noEmit and iterate (adjust the @types/node
version to match your Node runtime if needed) until the TypeScript build/lint
errors in buffer.d.ts and fs/promises.d.ts are resolved.

"vite": "^5.4.11",
"vitest": "^3.2.4"
},
Expand Down
Loading