Cotton Hou

I don't think the `void` could save you much here ```ts pipe( releaseOne(a), TE.map(() => releaseOne(b)), TE.apSecond(releaseOne(a + b)), ) ``` _If you go down that road, one may argue...

OK, let's take another angle: ```ts declare const acquire: TaskEither declare const use: (id: string) => TaskEither declare const release: (id: string) => TaskEither // how much resource left //...

I agree with you, I'm anything but against static typing, it just this very `void` type constraint acting weird, for the reference: ### **Fluture** ([doc], [dts]) ```haskell hook :: Future...

**tsc** targeting table: | main | module | | | :--- | :--- | - | | es5 | es5 | current `fp-ts` v**2.x** | | es5 | es2019 |...

Yeah, I know that `Pointed` typeclass sits in a [odd](https://wiki.haskell.org/Why_not_Pointed%3F) position in today's **FP** constructions, however for what it's worth, in current scope of `fp-ts` it still plays the `lifting`...

To be clear, this is only a suggestion that might fit with current `fp-ts` more economically, perhaps less correct in semantic terms.

This happens to me right after upgrading **Jest** from **v26** to **v27**, @sdomagala are you in the same condition as well?

By specifying `jest.useFakeTimers('legacy')` (instead of default `modern`) would mitigate the hanging for me. Quote from Jest blog post on **v27** release [1]: > Another default that we are changing affects...

Have just bumping into this with `rollup` setup, in such case, one need to set`treeshake.moduleSideEffects` to `false`, hope this helps.

Oh, forgot to mention, in rollup setup you need to exclude `pino-pretty` as well, like below ```javascript { treeshake: { moduleSideEffects: false, }, plugins: [ commonjs({ exclude: [ 'node_modules/pino-pretty/**', ],...