I think we should really expose the server as aedes.Server.

Basically we should add to aedes.js:

aedes.Server = aedes

In this way you can do:

import { Server, Client, AuthenticateError } from 'aedes'

This should not be a semver-major change, but just a facility for those using ESM and Typescript.

@mcollina what do you think about using default property instead?

Aedes.default = Aedes

This way the main function could be imported using default import syntax, while still exposing types if needed

import aedes, { Client, AuthenticateError } from 'aedes'  
// or Server, whatever default export name someone prefer

In fact, aedes can already be used this way with Babel or even with Typescript with esModuleInterop setting enabled. Unfortunately, by default TS module loader expects default property to be present.

Unfortunately, from what I've checked there is no way to change typings in a way that would allow both - current require syntax and default import in Typescript. This means that there would be a breaking change for people that currently use aedes in TS without esModuleInterop enabled.

I still think that default import is the way to go, especially for discoverability - when looking at JS examples, I think it's more obvious that const aedes = require('aedes') translates to import aedes from 'aedes' than to import { Server } from 'aedes', especially since with Babel a default import already works just fine.

If you don't want to introduce breaking changes or don't like default import syntax, I'll change it the way you suggested.

I would prefer the way I suggested, as it’s an additive change and it does not require a change in ts configuration.

I might have not explained it clearly - it wouldn't require ts configuration change, but change in the way it's currently imported. In any case, I added the Server property as you suggested.