Named exports used for tree-shaking

A package that only exports a single default namespace object forces bundlers to include the entire package in every consumer's bundle, regardless of which methods they actually use. ISO 25010 resource-utilization degrades linearly with how much dead code consumers are forced to carry. Tools like webpack, Rollup, and Vite perform tree-shaking on named exports but cannot eliminate unused properties of a default export object. For frontend consumers, this directly inflates page weight and Lighthouse scores.

Replace or supplement a default namespace export with named exports from src/index.ts.

// Before — single default object, not tree-shakeable:
const sdk = { createClient: () => {}, parseResponse: () => {} }
export default sdk

// After — named exports, each independently shakeable:
export function createClient() {}
export function parseResponse() {}
export function formatError() {}

A default export alongside named exports is acceptable if the class or factory function is the natural primary API. The key requirement: import { specificFunction } from 'your-package' must work without importing the rest.