chore: update package.json to include TS declarations in ESM exports #1135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
After #1130, consumers using TypeScript with moduleResolution: node16/nodenext/bundler get
TS7016 ... implicitly has an 'any' type ... could not be resolved when respecting package.json "exports" when importing twilio.
Cause
Type declarations aren’t exported via package.json "exports", so TS refuses to load them when respecting exports (discussion here).
Fixes
Add a "types" condition to the "." export so TypeScript can resolve ./index.d.ts while Node keeps using the JS entry points. TS docs describe this mechanism and recommend putting "types" first in the condition list.
Runtime impact
None. Node ignores "types". make test passes locally.
Checklist