fix: add types field to package.json

[erikras-gilfoyle-agent]

TypeScript types are generated and published to dist/index.d.ts but package.json has "types": null, preventing TypeScript from finding them.

This adds the missing types field to package.json.

Fixes #47

Summary by CodeRabbit

• Chores
  • Enhanced TypeScript support with improved type declaration configuration for better IDE integration and type checking.

[coderabbitai]

📝 Walkthrough

Walkthrough

Added the "types" manifest field to package.json, pointing to the TypeScript type declaration file at dist/index.d.ts. This ensures TypeScript projects can properly resolve the library's type definitions when consuming the package from npm.

Changes

Cohort / File(s)	Summary
Package Configuration package.json	Added "types" field to explicitly declare TypeScript type declaration file location, ensuring proper type resolution in consuming projects.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop and a skip, the types are in place,
No more TypeScript errors we need to erase,
The manifest now knows where to find declarations true,
Your IDE's now happy—and you are too! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a types field to package.json to resolve TypeScript type declaration issues.
Linked Issues check	✅ Passed	The PR directly addresses issue #47 by adding the missing 'types' field to package.json, enabling TypeScript to locate the generated declaration files in dist/index.d.ts.
Out of Scope Changes check	✅ Passed	The PR only modifies package.json to add the types field; all changes are directly related to resolving the linked issue with no out-of-scope modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/add-types-field

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}