esbuild_deno_loader
esbuild_deno_loader copied to clipboard
lucacasonato
Deno module resolution for `esbuild`
**Use Case** I frequently need to reload remote modules during development. In my use case, ESBuild is building a module from another localhost server. This localhost server will serve the...
I'm probably doing something wrong, but I was only able to move passed this by adding `npm:*` to my esbuild `externals` options. **Error** ``` error: Uncaught (in promise) Error: Build...
When setting up complicated esbuild configs, it's common to want to let other plugins handle certain specifiers. For example, `node:` might need to be handled by a polyfill plugin.
keeping compatibility with DENO_REGISTRY_URL
I'd love to use this to bundle resources that may include Deno code *and* non-JS code (like CSS/SCSS files). But adding the plugin to my ESBuild configuration breaks if there...
The docs state that the portable loader requires `--allow-read` and/or `--allow-net`, but the former is always required in fact. This seems to be because of the `Deno.cwd()` call. https://github.com/lucacasonato/esbuild_deno_loader/blob/ccd8992c690deee821d6b7a7efeaf599722c394c/src/plugin_deno_loader.ts#L187-L190 The...
The `esbuild_deno_loader` assumes that NPM packages are in a deno cache sub folder named `registry.npmjs.org` - ([see hard coded value here](https://github.com/lucacasonato/esbuild_deno_loader/blob/ccd8992c690deee821d6b7a7efeaf599722c394c/src/loader_native.ts#L109)) Unfortunately this assumption breaks now that Deno supports private...
For those who don't know, @twosaturdayscode has made a fork and rewrite at https://github.com/twosaturdayscode/esbuild-deno-plugin
#102 added support for marking specifiers as external, but it currently only works for specifiers such as `foo:bar` but not for a plain specifier such as `bar`. The test for...
Deno supports the following: when you put an `exports` section in your deno.json file as well as a package `name`, this implicitly adds an entry to your import map for...
