When deriving a Decoder for a generic Record, an empty object ({}) is always returned by decode:

const test: Decoder<Record<string, { foo: string; }>> = Derive();
test.decode({ bar: { foo: "hey" } });

returns

Right { right: {}, _tag: 'Right' }

Currently all modules are exported both as CJS and ESM, this while being a valid solution presents a fundamental issue;

packages can be either cjs or esm but can never be both, if for example one were to import a cjs dependency from an esm module we would end up with 2 copies of effect that share no state and are not interoperable, namely a lot will break.

What are the problems? generally any time we rely on state like Tags, FiberIDs, Lazy Values, Etc. Also guarding using instanceof isn't ok because class constructors are different.

Potential solution:

A single global package where we manage state, that package should be commonjs with an esm wrapper that re-export the package state.

Further infos: https://nodejs.org/api/packages.html#approach-2-isolate-state

Had a brief conversation with @schickling in discord about ArrayBuffers. Opening an issue to track the idea.

Links:

• https://github.com/GoogleChromeLabs/buffer-backed-object
• https://tc39.es/proposal-resizablearraybuffer/

In lue of a potential fp-ts reconciliation it would be better to isolate Prelude in it's own package (probably @effect/prelude) as it represents a port of concepts from zio-prelude (ideally using then HKT from fp-ts), and ideally we would have a similar package (@effect/fp-ts) that ends up exporting instances for fp-ts typeclasses