Michael Arnaldi

given README.md ends up in the npm package we might want to add a patch changeset

Yup that comes from 3.0.4, I don't see how this could ever be considered a bug of effect, it's behaviour of expect...

The Effect way of comparing options is `Equals.equals(a, b)`

Yeah but that's a bug in expect not in Effect... like I am trying to compare two objects with `a[Symbol.iterator] = [1, 2, 3, Math.random()][Symbol.iterator]` and it says that they...

seems like a vitest issue, jest had a similar https://github.com/jestjs/jest/issues/8280

https://github.com/vitest-dev/vitest/issues/5620

The following works: ```ts import { jestExpect as expect } from "@jest/expect" import { describe, it } from "vitest" describe("Vitest Issue", () => { it("compares", () => { const a...

I also confirm that the modules are invalid esm, as https://cdn.jsdelivr.net/npm/@opentelemetry/[email protected]/build/esnext/OTLPMetricExporter.js shows there is lack of '.js' extension in imports and this breaks usage. We are currently forcing usage of...

Not really if we keep the functions and effect returning functions separated On Fri, 15 Sept 2023, 17:10 Tim, ***@***.***> wrote: > ***@***.**** commented on this pull request. > ------------------------------...

Related fix: https://github.com/microsoft/TypeScript/pull/54183