ngasull
Bug in **native** loader. When linking a folder containing a workspace using [the new `links` option](https://deno.com/blog/v2.4#local-npm-packages), module resolution changes in a way that `esbuild-deno-loader` doesn't recognize workspace modules any more. In other words: loading linked workspace modules fail. **Important note**: using the deprecated `patch` option still works like before. This means its deno internals are slightly different than `links`. After investigation, I noticed that `esbuild`'s `onResolve` and `onLoad` don't resolve jsr imports the same way as before. - Using `patch`: provided namespace was `file` - Using `links`: provided namespace becomes `jsr` I could fix part of the issue locally in native loader by using the resolved `roots` provided by `deno info` and setting a redirection. However, fixing the shared resolver goes beyond my current knowledge of the project, esbuild and deno internals. --- Environment: - OS: NixOS - Deno version: v2.4.2 - esbuild plugin version: 0.11.1