SPWizard01

This is the one thing that actually blocks me from migrating from webpack to esbuild my entire app so I had to do compromises and split it, for now :)...

We use this to dynamically determine path for import outside of javascript. esbuild options: ```typescript ... platform: "browser", format: "esm", bundle: true, treeShaking: true, splitting: true, sourcemap: true, ... ```...

> The workaround is to use ``` import.meta.resolve ``` This would resolve relative to the module.

this is quite high impact for us, because having a lot of people within the company everyone types urls differently, this is especially bad when people type in the url...