[esbuild-plugin-meta-url] has no effect

I recently started a project which tries to implement a map renderer in Rust. I’m currently evaluating which bundler is the best for the task as I require two features:

• Inlining webworkers (or any module)
• Resolving/Handling import.meta.url in CJS and ESM modules, especially for .wasm files.

I tried the plugin @chialab/esbuild-plugin-meta-url to solve the second goal, but esbuild is not copying assets to the output directory.

Config:

build.mjs

import esbuild from 'esbuild';
import metaUrlPlugin from '@chialab/esbuild-plugin-meta-url';

await esbuild.build({
    entryPoints: ['src/index.ts'],
    bundle: true,
    format: "esm",
    platform: "browser",
    outdir: "dist/esbuild/",
    plugins: [
        metaUrlPlugin(),
    ],
});

Is there more configuration needed?

[edoardocavazza]

Hello @maxammann. We have released a new version of the plugin (0.15.17). As you suggested, we tried to closely match the standard URL behavior, so we started to prefer local imports over modules resolution. We still support it for backward compatibility, but now it raises a warning. Thank you!

[maxammann]

I kind of agree that resolving modules could be handy for users. I would put that under a feature flag though as it does not conform to the default behavior.

In plain ES6 new URL("test.js", import.meta.url), called from https://example.com/main.js will resolve to: https://example.com/test.js

That means by definition resolving a file though URL + import.meta.url is relative. When transforming such a URL construct we should keep the relativity.

I tried the current implementation against the generated code by wasm_bindgen which expects it to be foremost relative.