Skip to content

Conversation

@himanshusinghs
Copy link
Contributor

@himanshusinghs himanshusinghs commented Sep 4, 2025

Description

This PR proposes adding explicit type mappings in the exports entry of the package.json so that library consumers don't have to manually map types in their tsconfig, an example here.

What is changing?

We're adding an entry for types in the exports entry in package.json

Is there new documentation needed for these changes?

No

What is the motivation for this change?

We'd like to avoid doing explicit type mappings likes this.

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

  • Ran npm run lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@himanshusinghs himanshusinghs requested a review from a team as a code owner September 4, 2025 12:23
@himanshusinghs himanshusinghs changed the title chore: update exports entry with type mappings chore: update exports entry in package.json with type mappings Sep 4, 2025
@himanshusinghs himanshusinghs merged commit a40bacf into main Sep 4, 2025
30 checks passed
@himanshusinghs himanshusinghs deleted the chore/adding-type-mappings branch September 4, 2025 21:15
himanshusinghs added a commit that referenced this pull request Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants