Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.15.22.202
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
unp-musonza /
node_modules /
resolve-url /
Delete
Unzip
Name
Size
Permission
Date
Action
test
[ DIR ]
drwxr-xr-x
2021-02-04 21:24
.jshintrc
812
B
-rw-r--r--
2014-02-23 19:57
LICENSE
1.05
KB
-rw-r--r--
2014-02-23 19:01
bower.json
285
B
-rw-r--r--
2014-02-25 18:47
changelog.md
390
B
-rw-r--r--
2014-02-25 18:46
component.json
299
B
-rw-r--r--
2014-02-25 18:46
package.json
1.6
KB
-rw-r--r--
2021-02-04 21:24
readme.md
2.45
KB
-rw-r--r--
2014-02-25 18:44
resolve-url.js
1.04
KB
-rw-r--r--
2014-02-24 20:41
Save
Rename
Overview ======== [](https://ci.testling.com/lydell/resolve-url) Like Node.js’ [`path.resolve`]/[`url.resolve`] for the browser. ```js 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/ ``` Installation ============ - `npm install resolve-url` - `bower install resolve-url` - `component install lydell/resolve-url` Works with CommonJS, AMD and browser globals, through UMD. Usage ===== ### `resolveUrl(...urls)` ### 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`]. [`path.resolve`]: http://nodejs.org/api/path.html#path_path_resolve_from_to [`url.resolve`]: http://nodejs.org/api/url.html#url_url_resolve_from_to Tests ===== Run `npm test`, which lints the code and then gives you a link to open in a browser of choice (using `testling`). License ======= [The X11 (“MIT”) License](LICENSE).