[bug] cannot import Aedes when using TypeScript moduleResolution set to "node16"

[ZZwatermelon]

System Information

• Aedes: 1.0.1
• NodeJS: 22.22.0
• OS: Ubuntu 22.04.5
• Arch: x86_64

Describe the bug
When TypeScript moduleResolution is set to "node16", I am unable to import items in the same way as the examples:
import { Aedes } from 'aedes'
and instead get the following typescript error:
Module '"aedes"' has no exported member 'Aedes'.

To Reproduce
Steps to reproduce the behavior:

1. npm install aedes
2. set TypeScript moduleResolution to "node16"
3. Attempt to import Aedes

Expected behavior
Aedes should be properly imported.

Additional context
The issue is resolved if you switch moduleResolution to "bundler", but I presume this is still a bug as #1081 states it fixes this issue.

[robertsLando]

Thanks for reporting this.

The root cause is that the relative imports inside the .d.ts type definition files are missing .js extensions. With moduleResolution: "node16" and "type": "module" in package.json, TypeScript strictly requires file extensions on relative imports.

PR #1081 fixed the exports field in package.json (adding the types condition), which allows TypeScript to locate the entry point aedes.d.ts. However, once TypeScript reads that file, it encounters extensionless relative imports that fail under node16 resolution:

aedes.d.ts:

export * from './types/instance'  // should be './types/instance.js'
export * from './types/packet'    // should be './types/packet.js'
export * from './types/client'    // should be './types/client.js'

The same issue exists in the internal type files:

• types/client.d.ts — imports from './packet' and './instance'
• types/instance.d.ts — imports from './client' and './packet'
• types/packet.d.ts — imports from './client'

All of these need .js extensions to work under node16 module resolution. The bundler resolution mode is more lenient and resolves them without extensions, which is why it works there.

I'll open a PR with the fix.

[robertsLando]

@ZZwatermelon could you tell me if #1083 fixes your issue?

[ZZwatermelon]

#1083 does indeed fix it, thank you!