Is npm bugging you about this module being deprecated? You are probably depending on this module via the source-map-resolve package. For example:
nanomatch > snapdragon > source-map-resolve > resolve-url
The solution is to make your dependency chain update to source-map-resolve version 0.6.0 or later, or switch to dependencies not using source-map-resolve at all.
If you are looking for a way to resolve URLs in the browser, use URL.
Like Node.js’ path.resolve/url.resolve for the browser.
var resolveUrl = require("resolve-url")
window.location
// https://example.com/articles/resolving-urls/edit
resolveUrl("remove")
// https://example.com/articles/resolving-urls/remove
resolveUrl("/static/scripts/app.js")
// https://example.com/static/scripts/app.js
// Imagine /static/scripts/app.js contains `//# sourceMappingURL=../source-maps/app.js.map`
resolveUrl("/static/scripts/app.js", "../source-maps/app.js.map")
// https://example.com/static/source-maps/app.js.map
resolveUrl("/static/scripts/app.js", "../source-maps/app.js.map", "../coffee/app.coffee")
// https://example.com/static/coffee/app.coffee
resolveUrl("//cdn.example.com/jquery.js")
// https://cdn.example.com/jquery.js
resolveUrl("http://foo.org/")
// http://foo.org/npm install resolve-urlbower install resolve-urlcomponent install lydell/resolve-url
Works with CommonJS, AMD and browser globals, through UMD.
Pass one or more urls. Resolves the last one to an absolute url, using the
previous ones and window.location.
It’s like starting out on window.location, and then clicking links with the
urls as href attributes in order, from left to right.
Unlike Node.js’ path.resolve, this function always goes through all of the
arguments, from left to right. path.resolve goes from right to left and only
in the worst case goes through them all. Should that matter.
Actually, the function is really like clicking a lot of links in series: An
actual <a> gets its href attribute set for each url! This means that the
url resolution of the browser is used, which makes this module really
light-weight.
Also note that this function deals with urls, not paths, so in that respect it
has more in common with Node.js’ url.resolve. But the arguments are more
like path.resolve.
First off, run npm install to install testing modules.
npm test lints the code and then gives you a link to open in a browser of
choice (using testling).
package.json, component.json and bower.json are all generated from
x-package.json5 by using xpkg. Only edit x-package.json5, and remember to
run xpkg before commiting!