Fixes #1105 by adding RestException to the main package exports, allowing developers to import it directly from 'twilio' instead of using deep imports.

Problem

Previously, developers had to use deep imports to access RestException:

// Old approach - problematic with modern TypeScript configs
import RestException from 'twilio/lib/base/RestException'

This caused issues with modern TypeScript configurations and wasn't intuitive for developers who expected to import it from the main package like other Twilio components.

Solution

Added RestException to the main package exports following the same pattern used by other components like RequestClient:

// Now supported - clean and intuitive
import { RestException } from 'twilio'

// Also works with CommonJS
const { RestException } = require('twilio')

Changes

• Added RestException import to src/index.ts
• Added both type and value exports to the TwilioSDK namespace
• Maintains full TypeScript support with proper type definitions

Usage Examples

Error Handling:

import { RestException } from 'twilio';

try {
  // Twilio API call
} catch (error) {
  if (error instanceof RestException) {
    console.log(`Twilio Error ${error.code}: ${error.message}`);
    console.log(`Status: ${error.status}`);
    console.log(`More info: ${error.moreInfo}`);
  }
}

CommonJS:

const { RestException } = require('twilio');
const exception = new RestException(response);

Validation

• All existing tests pass (316/316)
• TypeScript compilation succeeds
• No breaking changes to existing functionality
• Follows established export patterns in the codebase

This change provides a better developer experience while maintaining backward compatibility and following the library's existing conventions.

💡 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.