With the advent of Deno v1.45, Deno now has first class support for "npm workspaces", and better Node interop. We should look at the various Deno-specific parts of our codebase and consider the how best to simplify building, packaging, and publishing for Deno consumers.
Can we bring the Deno packaging into the main edgedb-js monorepo from the separate edgedb-deno repo?
Do we even need a separate build anymore? Maybe node-compat is good enough now?
Should dual-publish to JSR?
Can we split the driver and generator for Deno to match that split in our npm packaging?
With the advent of Deno v1.45, Deno now has first class support for "npm workspaces", and better Node interop. We should look at the various Deno-specific parts of our codebase and consider the how best to simplify building, packaging, and publishing for Deno consumers.
edgedb-jsmonorepo from the separateedgedb-denorepo?