Upgrade to TypeScript ~6.0.3 #19
No reviewers
Labels
No labels
app
bug
ci
compliance
dependencies
docs
documentation
duplicate
enhancement
good first issue
help wanted
infra
invalid
javascript
python
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: adam/exec-aide#19
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feature/typescript-6-upgrade"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
typescriptfrom ~5.7.2 to ~6.0.3"types": ["node"]totsconfig.json— required by TS 6 to resolve Node globals (path,__dirname)Supersedes Dependabot PR #8.
Test plan
tsc --noEmitpasses cleanlyPR Summary
Low Risk
Low risk: dependency/config-only change, but TypeScript 6 may surface new typechecking or build-time incompatibilities in CI/CDK synth steps.
Overview
Upgrades the project’s TypeScript toolchain from
~5.7.xto~6.0.3(including lockfile updates).Updates
tsconfig.jsonto explicitly include Node typings via"types": ["node"]to keep Node globals/modules resolving correctly under TS6.Reviewed by Cursor Bugbot for commit
f27bb1acdf. Bugbot is set up for automated code reviews on this repo. Configure here.Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit
c4c7d423b9. Configure here.Lockfile incorrectly marks direct dependencies as peer-only
Medium Severity
aws-cdk-libandconstructsare direct productiondependenciesinpackage.json, but the regeneratedpackage-lock.jsonincorrectly marks them with"peer": true. This is a known npm bug where packages satisfying both a direct dependency and another package's peer dependency get flagged as peer-only. Runningnpm ci --omit=peerwould skip these production dependencies entirely. Regenerating the lockfile with npm ≥ 11.6.3 (which fixed this bug) would resolve the issue.Additional Locations (1)
package-lock.json#L588-L590Reviewed by Cursor Bugbot for commit
c4c7d423b9. Configure here.