Drop CJS

Linking the same issue in effect-ts.

As you may already know, there’s an ongoing effort to find common ground with effect-ts and unify the ecosystem.

Effect will be ESM only from 31/12/2022.

I propose to switch to ESM only (fp-ts v3 and its alpha releases).

[kungfooman]

So how many hours did you waste now by doing it “properly” by testing all kinds of plugins with extra bells and whistles?

I got ESM to work with ONE regex 😂

Good job I guess, professionals…

[mikearnaldi]

@mikearnaldi It works! Thanks!

Off topic: Why are all the useful things in @fp-ts/data? What is @fp-ts/core for?

You’re welcome!

So the idea is to separate a bit the implementations to keep it more maintainable and focused, in /core we have only abstractions that general but that at the same time are rarely useful from the user perspective, a normal user will interact mostly with specific packages, the plan is:

• @fp-ts/data => all the common data structures
• @fp-ts/codec => similar to io-ts focused on domain modelling
• @fp-ts/optic => similar to monocle
• @effect/io => effect execution
• @effect/stream => streaming focused
• etc

You can check the repositories in the orgs, in the one for /core there is some kind of initial explainer of what we have in mind:

• https://github.com/fp-ts
• https://github.com/Effect-TS