Support for relative URLs

[samanson123]

The package doesn't seem to be work with applications that require relative URLs.

For example, I intend to host my application as an IIS web application meaning it won't be hosted under the root DNS. The BlazorJSComponents.lib.module.js file imports from '/_content/BlazorJSComponents/component.mjs' which causes a 404 error.

Tried running under .NET 9, Blazor static SSR hosted on IIS.

I've had to do a bit of hacky fix in the meantime where I generate the default import map as a string using HtmlRenderer and then replace the existing map which uses ./ at the start (the default it expects) to / as is in the JavaScript file and then map back to ./

[mnbob70]

I'm having this issue as well. Tried moving from development to our IIS server. It fails to find the mjs file when running as an Application under the Default Website. This was the only solution I could find that allowed me to co-locate JavaScript for components running purely as Blazor SSR. edit removed additional comment that turned out to be wrong info

[mnbob70]

@samanson123 I had basically no knowledge of javascript modules, but thanks to your description I did some research and came up with the following relatively straight forward workaround in App.razor by adding the following script tag in front of ImportMap.

    <script type="importmap">
        {
            "imports": {
                "/_content/BlazorJSComponents/component.mjs": "./_content/BlazorJSComponents/component.mjs"
            }
        }
    </script>
    <ImportMap />