Debian Codegraph @

debian/control

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