Sebastian Lorenz
Sebastian Lorenz
This also happens under certain circumstances (not yet entirely sure how to reproduce this reliably) when using `pnpm` with symlinked node modules that host smart contracts (e.g. openzeppelin, etc.)
We've rolled our own basic connect-node interceptors for now. This lets us collect some generic metrics & tracing via OpenTelemetry and Sentry.io but also gives us a way to "enhance"...
Just a side note related to traces for those of us who are using sentry.io. Especially in case of streaming responses and long running requests or simply high throughput APIs...
Both seem a bit awkward tbh. Also, apologies in advance as I'm probably missing something here, but why would you ever want to use the `Data.proxy()` and then set `deep`...
> Having an object / array already constructed and wanting to have a view (proxy) which compares by value instead of by reference Yes, I get that, but my question...
Could this be an option too? ```ts import { Data } from "effect" class User extends Data.Class
> @fubhy I have built a Timezone type for this. I am testing it now. Do you have a preference for how it integrates into Cron, dayOfWeek, ... > >...
The main hurdle I can see so far is that `vitest` doesn't play well with Deno afaik.
As you mentioned, Deno is not 100% compat with Node. Hence, to prove that `effect` and `@effect/platform` works with Deno (and fix any possible instances where it doesn't) you'd have...