chore(deps): apply the dependency updates 1.2.0 claimed - #14
Merged
Conversation
1.2.0 shipped with a changelog entry listing TypeScript 7, pg to 8.23, @inquirer/prompts and @biomejs/biome. Those updates were never applied here — only to the redis analyzer — so the entry described a release that did not exist. The entry is corrected and the updates ship in 1.3.0. Applying them surfaced a real problem: TypeScript 7 no longer reliably auto-includes @types/node, and without it every Node global — console, process, URL, setTimeout — failed to resolve. tsconfig now names it explicitly, which is what the compiler's own diagnostic recommends. Verified against a real database container through both the CLI and the programmatic API: full analysis, health scoring and report generation.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Correcting a mistake in 1.2.0. Its changelog entry listed TypeScript 7,
pg,@inquirer/promptsand@biomejs/biomeupdates. Those were only ever applied to the redis analyzer —pnpm addwas run there and not here — so 1.2.0 described a release that did not exist. The 1.2.0 entry is corrected to say what it actually contained (the Node 22 floor, thenodenextmove and the Actions bumps), and the dependency updates ship here as 1.3.0.What actually landed now
pg8.23,@types/pg8.23,@inquirer/prompts8.7.2,@biomejs/biome2.5.12.A real bug this surfaced
TypeScript 7 no longer reliably auto-includes
@types/node. Without it, every Node global failed to resolve —console,process,URL,setTimeout, theNodeJSnamespace — 153 compile errors. The remedy is naming it explicitly intsconfig.json, which is exactly what the compiler's own diagnostic recommends.Worth noting this was invisible until the driver bump forced a real type-check: the redis analyzer happened to still resolve the globals with the same config, so the three repos silently diverged.
Verification
Not a green type-check alone. Exercised against a real
postgres:17-alpinecontainer through both the CLI and the programmatic API — full analysis, health scoring, report generation — pluspnpm lint,pnpm buildand all 40 tests.