1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
Source: node-url-parse
Section: web
Priority: extra
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Uploaders: Thorsten Alteholz <debian@alteholz.de>
Build-Depends:
debhelper (>= 9)
, dh-buildinfo
, nodejs
, mocha
, node-object-inspect
, node-requires-port
, node-querystringify
, node-deep-eql
Standards-Version: 3.9.6
Homepage: https://github.com/unshiftio/url-parse#readme
Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-url-parse.git
Vcs-Browser: https://anonscm.debian.org/gitweb/?p=pkg-javascript/node-url-parse.git
Package: node-url-parse
Architecture: all
Depends:
${misc:Depends}
, nodejs
, node-requires-port (>= 0.0.1)
, node-querystringify (>= 0.0.3)
Description: Parse URL in node using the URL module and in the browser using the DOM
The url-parse method exposes two different API interfaces. The url interface
that you know from Node.js and the new URL interface that is available in
the latest browsers.
.
Since 0.1 we've moved away from using the DOM's <a> element for URL parsing
and moving to a full Regular Expression solution. The main reason for this
change is to make the URL parser available in different JavaScript
environments as you don't always have access to the DOM like Worker
environments. This module still have a really small foot print as this
module's main intention is to be bundled with client-side code. The only
problem however with a RegExp based solution is that it required a lot of
lookups causing major problems in FireFox. So the last and the current
solution was a pure string parsing solution which chops up the URL in
smaller pieces.
.
Node.js is an event-based server-side JavaScript engine.
|
