Sebastian Lorenz

> You should consider that in practical usage caching the results of query parsing means that the efficiency of the query parsing is fairly unimportant. We've yet to open source...

I am super interested. :)

I am also interested in this for 2 libraries that I am working on for which I'd like to use flummox without leaking "my flux" down blindly. Is there anything...

I am also seeing this error when trying to publish from a subdirectory. Running `yarn publish dist` manually works however.

This is harder to implement then it looks on the surface if you want to include: - re-establish subscriptions after reconnecting - queue and re-send queued requests after the connection...

@fvictorio Have you considered stuff like esbuild / esbuild-kit (https://github.com/esbuild-kit)? We leverage that toolchain to enable `vitest` to work with hardhat. And I'm also happily using `tsx` and `tsup` elsewhere....

Maybe this is the time to re-evaluate full ESM compatibility?

> > Maybe this is the time to re-evaluate full ESM compatibility? > > "Full ESM compat" is impossible in hardhat before the next major. Hardhat's task system relies entirely...

What I'm saying is: Let's modularize the core components of hardhat and expose some of the underlying bits that are also useful outside of the task runner mode of operation...

Thanks @alcuadrado. Just to be clear I definitely don't want to derail this effort or distract you from your roadmap. I am just really eager to delete as much of...