Fix TypeScript named import support for Twilio client #1109
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.
Fixes #935 where importing
{ Twilio }
from the library resulted in TypeScript inferring the type asany
instead of the properTwilio
class type.Problem
Users trying to use ES6 named imports would encounter type issues:
The root cause was that the library used
export = TwilioSDK
syntax throughout, which requiresesModuleInterop: true
in TypeScript configuration to work properly with named imports. Without this setting, TypeScript couldn't resolve the named exports correctly.Solution
Modified
src/index.ts
to provide both ES6 named exports and CommonJS compatibility:export = TwilioSDK
export const Twilio
,export const jwt
, etc.) +export default TwilioSDK
This generates a
lib/index.d.ts
file that supports all import patterns:Testing
The fix ensures users can use modern ES6 import syntax without requiring specific TypeScript configuration, while maintaining full backward compatibility.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.