ESM support: package does not expose an ES module entry

[zckrs]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

Hello 👋

Currently, @fastify/sse does not expose an ESM-compatible entry point.

Lack of ESM support makes integration harder or forces workarounds such as createRequire, which is not ideal.

Is ESM support planned for @fastify/sse?

Motivation

No response

Example

No response

[SlugFiller]

Although slightly unintuitive, this has worked for me:

import sse from '@fastify/sse';

try {
	const server = fastify();

	await server.register(sse.default);

	const address = await server.listen({ host: '::', port: 8080 });

	console.log(`Server listening at ${address}`);
}
catch (err) {
	console.error(err);
}

The .default seems to be necessary, as TypeScript emits an error otherwise.

[stephen-carter-at-sf]

I also just ran into this issue because my node package type for my service is "module". I confirm that sse.default works but is a clunky looking workaround.

[kibertoad]

@mcollina How can I release a new version of the module? I cannot bump the version directly anymore.

[zckrs]

Hi, @kibertoad

can you release a new patch ?

You can use https://www.npmjs.com/package/np to easily fire a release on github + npm with a bump of package.json and redact changelog.

npx np