'root-relative' urls are not resolved correctly about html-loader HOT 10 CLOSED

I think this issue may apply to other loaders that try to resolve paths from embedded urls as well, such as css-loader and less-loader.

from html-loader.

I think my expectation of how this would work is that the 'root-relative' urls would be resolved against the module root(s). Basically, instead of prepending with ./, stripping the leading / from the the url.

In fact, making the following change to urlToRequire seems to solve my use case:

function urlToRequire(url) {
    if(/^~/.test(url))
        return url.substring(1);
    else if(/^\//.test(url))
        return url.replace(/^\/+/, '');
    else
        return "./"+url;
}

This also seems relevant to the similar functionality in css-loader.

from html-loader.

Mhmmm ... I'd expect absolute paths being resolved relative to resolve.root.

from html-loader.

I thought of a query parameter root:

• root not set: Root-relative urls are threaded like absolute urls and are not translated.
• root set: root is prepended to root-relative urls and they are translated

from html-loader.

Why is it a query parameter? Is it likely to have different roots?

from html-loader.

It doesn't seem very likely that there would be different roots for a given build, but it does seem likely that the root would need to be configured (and differently from resolve.root.) Is there a better way to do that?

from html-loader.

Since #8 is now closed, i think this one can be closed, too!

from html-loader.

How does the root-query param work?

from html-loader.

https://github.com/webpack/html-loader#root-relative-urls

from html-loader.

K thx

from html-loader.