Carlos Esteban Lopez Jaramillo

I just ran into this, came from the neo4j/graphql issue mentioned, the workaround is still valid but its a very obscure error, took me 3 days of searching until I...

Hi there, I found this error again, this time in a different context, it was in the API when creating the Apollo server instance, and for this case, the workaround...

I deleted a comment about a different bug, the `overrides` do work though I'm using `pnpm` so I had to do `pnpm.overrides` in the `package.json`, still it is an obscure...

@phryneas It is indeed a weir case, to clarify my situation, I have an Nrwl Nx Monorepo with Next.js configured, but I don't have this in the main app, I...

> You might try to use a `package.json` [`overrides`](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides) field to specify if you want to use `superjson` version 1 or 2 - I believe v1 is commonJs, while v2...

Wow, those are a lot of file changes, seems like you even moved stuff out of the global window, I'm not confident in my React & Next knowledge to understand...

@phryneas I installed the PR commit, removed the npm overrides (`pnpm.overrides` in my case), ~~and ran my app, works like a charm, not sure what other cases we can test,...

On the other hand, I went and installed the latest `0.8.0`, removed the overrides and the tests work ok now (though I did have to wrap my components in ``...

These are the only references I could find, not much to go off, its basically so new that there are no docs about it: https://nodejs.org/api/timers.html#immediatesymboldispose https://nodejs.org/api/events.html#eventsaddabortlistenersignal-listener https://nodejs.org/api/child_process.html#subprocesssymboldispose https://github.com/search?q=repo%3Anodejs%2Fnode+symbol.dispose&type=code

@benjamingr Worry not, I'm not gunning for this feature just yet, I know tc39 is in stage 3 draft, I just came here out of curiosity as someone was showing...