node package manager

Introducing npm Enterprise add-ons. Integrate third-party dev tools into npm…


Like Node.js’ <code>path.resolve</code>/<code>url.resolve</code> for the browser.


Like Node.js’ path.resolve/url.resolve for the browser.

var resolveUrl = require("resolve-url")
// Imagine /static/scripts/app.js contains `//# sourceMappingURL=../source-maps/` 
resolveUrl("/static/scripts/app.js", "../source-maps/")
resolveUrl("/static/scripts/app.js", "../source-maps/", "../coffee/")


  • npm install resolve-url
  • bower install resolve-url
  • component 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 functions 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.


Run npm test, which lints the code and then gives you a link to open in a browser of choice (using testling).


The X11 (“MIT”) License.