David
70072d39e3
An ES module TypeScript consumer was given the CommonJS declarations in dist/types. With those,
`import alex2node from "alex2node"` compiled (module Node16) and then failed when Node loaded it: "The requested
module 'alex2node' does not provide an export named 'default'". The ES module build has named exports only.
tsconfig.esm.json now emits declarations next to dist/esm/*.js, under that directory's {"type": "module"}, and
"exports" selects per condition: import -> dist/esm/index.d.ts, require -> dist/types/index.d.ts. The default
import is now refused with TS1192; named imports are unchanged. "main", "module" and "types" are as before.
test/fixtures/types.mts holds the default import under @ts-expect-error, and a new test requires "types" before
"default" and a declaration for every built file. dist/: 25 files, 132,291 B -> 33 files, 155,647 B; the npm
tarball 25,125 B -> 25,837 B. npm test: 25 pass in 5.6 s.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
13 lines
749 B
TypeScript
13 lines
749 B
TypeScript
// Compiled, never run: an ES module TypeScript consumer. The "import" condition in "exports" gives it the
|
|
// declarations next to the ES module build (dist/esm/*.d.ts), which has named exports only. Read through the
|
|
// CommonJS declarations in dist/types, the default import below compiles and then fails when Node loads it.
|
|
import { Alex2MQTT, DEFAULT_HOST, EndpointHealth } from "alex2node";
|
|
import type { Device } from "alex2node";
|
|
// @ts-expect-error the ES module build has no default export
|
|
import alex2node from "alex2node";
|
|
|
|
const bridge = new Alex2MQTT("user", "password", "root", false, { host: DEFAULT_HOST });
|
|
const devices: Device[] = bridge.getDevices();
|
|
const health: EndpointHealth = EndpointHealth.OK;
|
|
|
|
export { devices, health };
|