Skip to content

Strict typing configuration#9

Merged
jmlweb merged 1 commit intomainfrom
cursor/strict-typing-configuration-b081
Dec 25, 2025
Merged

Strict typing configuration#9
jmlweb merged 1 commit intomainfrom
cursor/strict-typing-configuration-b081

Conversation

@jmlweb
Copy link
Copy Markdown
Owner

@jmlweb jmlweb commented Dec 25, 2025

Configure strict typing by enabling stricter TypeScript compiler options and resolving newly surfaced type errors.

The exactOptionalPropertyTypes flag surfaced a real typing issue in lruCache.ts where an optional property was explicitly set to undefined instead of being omitted. Additionally, a flaky timing assertion in delay.test.ts was stabilized due to timer resolution inconsistencies.


Open in Cursor Open in Web


Note

Strengthens type safety and aligns code with stricter compiler checks.

  • TS config tightened in tsconfig.json (e.g., isolatedModules, noFallthroughCasesInSwitch, noPropertyAccessFromIndexSignature, noUncheckedIndexedAccess, exactOptionalPropertyTypes, useUnknownInCatchVariables), and project includes/excludes updated.
  • LRU cache typing fix: set now omits expiration when undefined instead of setting it to undefined, complying with exactOptionalPropertyTypes.
  • Test deflake: delay.test.ts relaxes minimum elapsed threshold (>=45ms) to account for timer resolution.

Written by Cursor Bugbot for commit 0deaf27. This will update automatically on new commits. Configure here.

Co-authored-by: josemanuel <josemanuel@jmlweb.es>
@cursor
Copy link
Copy Markdown
Contributor

cursor bot commented Dec 25, 2025

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@jmlweb jmlweb marked this pull request as ready for review December 25, 2025 13:27
@jmlweb
Copy link
Copy Markdown
Owner Author

jmlweb commented Dec 25, 2025

@cursoragent

@jmlweb jmlweb merged commit 9952f88 into main Dec 25, 2025
3 checks passed
@github-actions
Copy link
Copy Markdown

🎉 This issue has been resolved in version 1.11.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants