baetheus / pick / 22206807738

87%

push

github

feat: cleaned up builder_client.ts a bit

Unseen here is about half a day of trying esbuild-wasm, esbuild, and
Deno.bundle across deno.land/x, local wasm blobs, and npm. What I have
learned is that any wasm esbuild version will fail to resolve npm:
specifiers. Additionally, static esbuild runs into several issues around
requiring run access (a non-starter) or copious env access. Deno.bundle,
surprisingly, requres the unstable-bundle flag, read, and write (for
temp files), which is currently the most stable and *least* invasive
option. However, it still fails to run on Deno Deploy (there goes
my free hosting), so nix packaging is now on the docket.

Ultimately, Deno.bundle is a built in and will likely be the fastest and
most portable (eventually) of the bundle options I found. It still does
not tree shake and does not have support for a plain text entrypoint,
but the tempfile solution is ok for now. This will effectively force me
to learn how to easily package pick based deno apps with nix for use as
nixos modules. Yay, more research. Despite my exhaustion from finding
all the edge cases of deno and esbuild I am excited to finally have an
easymode, no fuss router/builder pair to start rebuilding me web
projects in.

There is a simple-ish path to split builder into dev/prod paths, but I
am currently exhausted from this project and want to move on to a couple
of easy tools, starting with blaylock.dev. Wish me luck, non-existent
reader!

33 of 43 branches covered (76.74%)

Branch coverage included in aggregate %.

109 of 130 new or added lines in 1 file covered. (83.85%)

1133 of 1291 relevant lines covered (87.76%)

19.05 hits per line