feat: Upgrade TypeScript to v5.9.2

[Copilot]

This PR upgrades TypeScript from version 5.3.3 to 5.9.2, bringing the project up to the latest stable release in the 5.9 series.

Changes Made

• Updated the main package.json to use typescript: "^5.9.0"
• Enhanced .gitignore to prevent TypeScript build artifacts from being committed in src directories
• Updated @types/node to v24.3.0 to resolve compatibility issues with TypeScript 5.9
• Verified all builds, type checks, and functionality work correctly with the new version

Testing

All existing builds and type checks pass successfully with TypeScript 5.9.2:

• ✅ npm run build - All packages build correctly
• ✅ npm run typecheck - Type checking passes for all packages
• ✅ No breaking changes or compatibility issues found

The upgrade maintains full backward compatibility while providing access to the latest TypeScript features and improvements in the 5.9 release line.

Fixes #30.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[Copilot]

@lxcid 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.

[lxcid]

lgtm

[lxcid]

bump to 5.9? @copilot

[Copilot]

bump to 5.9? @copilot

Updated to TypeScript 5.9.2! Also updated @types/node to v24.3.0 to resolve compatibility issues. All builds and type checks pass successfully. (44c6858)

[lxcid]

@copilot rebase

[Copilot]

@copilot rebase

I cannot perform a git rebase directly due to technical limitations (no force push access). The master branch has newer commits (dependency updates) that would conflict with the package-lock.json changes from the TypeScript upgrade.

To rebase this PR, you would need to:

1. Fetch the latest master branch
2. Run git rebase master on this branch
3. Resolve conflicts in package-lock.json and package.json
4. Force push the rebased branch

Would you like me to attempt an alternative approach, or would you prefer to handle the rebase manually?