Head's up: plug-compile removing --importmap option (and esbuild update)

Recent Deno version included a regression (later fixed I think) that caused imports to fail for plug builds. This escalated into some push from the Deno community to switch SilverBullet's plug-compile code to use @deno/esbuild-plugin - JSR instead of the legacy plugin we used before.

This all seems to work, but cannot support specific importmaps, so I had to remove the --importmap option from plug-compile. For as far as I can see most plug builds use the -c option to pass in a deno.json file (which can include an import map directly), but those who who still rely on explicit import maps, please move your imports to your deno.json file and use the -c option.

The new version of deno-compile should be part of the edge builds soon (which many of you use by default). Please check if your builds still work.

1 Like

Does that mean we can finally import files as raw strings? So we can get rid of all the html as big strings files (like the panel_html file for example)?

1 Like

You can try

1 Like