Dynamic import of .ts files do not get transpiled

[martijnvankreij-dev]

I am using the latest version of esbuild to bundle an application that dynamically tries to import a given .js file. When running I receive the following warning: [WARNING] The glob pattern import("./**/*.js") did not match any files [empty-glob]

I was assuming that esbuild would transpile the .ts files to .js files and that the import wouldn't be a problem. Is this by design, and are there workarounds? Making the .ts files also entrypoints doesn't seem to make a difference.

The minimal reproduction can be seen here.

[hyrious]

import(`./${name}.ts`) should work. The glob import seems only matches the full, original path.

[davidwalschots]

I can imagine there are scenarios where dynamically importing *.ts files doesn't work. E.g. when using Web Dev Server (WDS) to develop on your local machine, and using esbuild as part of the build/deploy of the application. WDS would compile and serve the TypeScript as *.js files, and things would break when trying to import *.ts.

This might be "solved" by writing:

location.hostname === "localhost" ? import(`./${name}.js`) : import(`./${name}.ts`);

But of course the above requires that the code that performs the dynamic import is authored by the user, and not part of some imported package.