fix: Use default export conditions instead of import

[beeequeue]

This change allows the package to be imported with require(esm)

This is what is shown with the current export conditions:

Screenshot

But it works with default:

Screenshot

And older node versions without require(esm) get a clearer error:

Screenshot

[lukeed]

What’s the current error message for Node 18 doing a require?

I think the recommended approach is to use “module-sync” instead of adding an ambiguous default?

If Node18 error with current configuration is clear I think module-sync is way to go

[beeequeue]

The current error in node 18 is the same as the first image - not very clear what the error actually is.

module-sync gives the same unclear error as import in node 18, so it's up to you what you think is better

[lukeed]

Thanks. I'll merge, but I think I'm going to just include require exports, actually. I took a look around this morning & still so much of tooling ecosystem is using require-only builds, so these changes wouldn't help them either 😞

[beeequeue]

That would be very nice, I have looked into 3 packages where neither empathic or find-up-simple work because they need find.any which simple doesn't have, and can't use ESM!