Actualizacion maquina principal

[dotfiles/.git] / .config / coc / extensions / node_modules / coc-prettier / node_modules / resolve-url / readme.md

diff --git a/.config/coc/extensions/node_modules/coc-prettier/node_modules/resolve-url/readme.md b/.config/coc/extensions/node_modules/coc-prettier/node_modules/resolve-url/readme.md
new file mode 100644 (file)
index 0000000..edfff73
--- /dev/null
+++ b/.config/coc/extensions/node_modules/coc-prettier/node_modules/resolve-url/readme.md
@@ -0,0 +1,83 @@
+Overview\r
+========\r
+\r
+[![browser support](https://ci.testling.com/lydell/resolve-url.png)](https://ci.testling.com/lydell/resolve-url)\r
+\r
+Like Node.js’ [`path.resolve`]/[`url.resolve`] for the browser.\r
+\r
+```js\r
+var resolveUrl = require("resolve-url")\r
+\r
+window.location\r
+// https://example.com/articles/resolving-urls/edit\r
+\r
+resolveUrl("remove")\r
+// https://example.com/articles/resolving-urls/remove\r
+\r
+resolveUrl("/static/scripts/app.js")\r
+// https://example.com/static/scripts/app.js\r
+\r
+// Imagine /static/scripts/app.js contains `//# sourceMappingURL=../source-maps/app.js.map`\r
+resolveUrl("/static/scripts/app.js", "../source-maps/app.js.map")\r
+// https://example.com/static/source-maps/app.js.map\r
+\r
+resolveUrl("/static/scripts/app.js", "../source-maps/app.js.map", "../coffee/app.coffee")\r
+// https://example.com/static/coffee/app.coffee\r
+\r
+resolveUrl("//cdn.example.com/jquery.js")\r
+// https://cdn.example.com/jquery.js\r
+\r
+resolveUrl("http://foo.org/")\r
+// http://foo.org/\r
+```\r
+\r
+\r
+Installation\r
+============\r
+\r
+- `npm install resolve-url`\r
+- `bower install resolve-url`\r
+- `component install lydell/resolve-url`\r
+\r
+Works with CommonJS, AMD and browser globals, through UMD.\r
+\r
+\r
+Usage\r
+=====\r
+\r
+### `resolveUrl(...urls)` ###\r
+\r
+Pass one or more urls. Resolves the last one to an absolute url, using the\r
+previous ones and `window.location`.\r
+\r
+It’s like starting out on `window.location`, and then clicking links with the\r
+urls as `href` attributes in order, from left to right.\r
+\r
+Unlike Node.js’ [`path.resolve`], this function always goes through all of the\r
+arguments, from left to right. `path.resolve` goes from right to left and only\r
+in the worst case goes through them all. Should that matter.\r
+\r
+Actually, the function is _really_ like clicking a lot of links in series: An\r
+actual `<a>` gets its `href` attribute set for each url! This means that the\r
+url resolution of the browser is used, which makes this module really\r
+light-weight.\r
+\r
+Also note that this functions deals with urls, not paths, so in that respect it\r
+has more in common with Node.js’ [`url.resolve`]. But the arguments are more\r
+like [`path.resolve`].\r
+\r
+[`path.resolve`]: http://nodejs.org/api/path.html#path_path_resolve_from_to\r
+[`url.resolve`]: http://nodejs.org/api/url.html#url_url_resolve_from_to\r
+\r
+\r
+Tests\r
+=====\r
+\r
+Run `npm test`, which lints the code and then gives you a link to open in a\r
+browser of choice (using `testling`).\r
+\r
+\r
+License\r
+=======\r
+\r
+[The X11 (“MIT”) License](LICENSE).\r