garycourt/uri-js

Issues

• DeprecationWarning: The `punycode` module is deprecated

  #96 opened 6 months ago by lorezyra
  1

• punycode is deprecated, remove dependency

  #94 opened 8 months ago by stheine
  10

• This library does not handle special signs in uri path segments

  #93 opened 8 months ago by steve-todorov
  2

• potential security vulnerability

  #92 opened 10 months ago by ranjit-git
  1

• Export types other than `URIComponents`

  #91 opened a year ago by dmsehuang
  0

• Package Vulnerability: path-parse: 1.0.5

  #84 opened 2 years ago by oliviercperrier
  1

• CVE-2021-44906 in transitive dependency

  #72 opened 2 years ago by mcharno
  4

• Tag for 4.4.1 missing

  #88 opened a year ago by pombredanne
  0

• License not found for [@uri-js 4.4.1]

  #81 opened 2 years ago by RohaitKS
  2

• Inconsistent license?

  #87 opened a year ago by pombredanne
  0

• How do you parse the subdomain with this?

  #85 opened a year ago by koodinmies
  0

• Package Vulnerability: minimatch:3.0.4

  #83 opened 2 years ago by oliviercperrier
  0

• Replace qunit

  #79 opened 2 years ago by thernstig
  0

• CVE-2021-3807 in ansi-regex dependency

  #78 opened 2 years ago by mangopeaches
  0

• Please tag 4.4.1 on Github

  #68 opened 2 years ago by mohe2015
  0

• Trying to get in touch regarding a security issue

  #65 opened 3 years ago by JamieSlome
  4

• Invalid IDN decoding

  #70 opened 3 years ago by socketpair
  0

• NPM package dscription does not match repo

  #69 opened 3 years ago by Gixen
  0

• WS URI parsing not RFC conform?

  #62 opened 3 years ago by fexpal
  0

• Documented as Validating

  #60 opened 3 years ago by dhurlburtusa
  0

• yarn lock locks down growl@1.9.2 but this version has vulnerabilities

  #54 opened 3 years ago by clisterdmello
  2

• Possible vulnerability

  #59 opened 3 years ago by pavoltravnik
  2

• Resolving URNs with resolveComponents returns urn:undefined:undefined

  #38 opened 4 years ago by ucarion
  2

• Support ws and wss protocols

  #39 opened 4 years ago by grantwwu
  4

• Slow _normalizeIPv6

  #40 opened 4 years ago by mcollina
  2

• Invalid scheme syntax permitted

  #35 opened 4 years ago by palemieux
  1

• Reduce the size of the npm package by limiting the included files

  #36 opened 4 years ago by paazmaya
  3

• URI.serialize ignores String port

  #46 opened 4 years ago by polmabri
  0

• Add support for parsing query string into object

  #34 opened 6 years ago by chefhoobajoob
  1

• Create ES5+Modules dist

  #32 opened 6 years ago by garycourt
  3

• Issue when building using create-react-app

  #33 opened 6 years ago by DanielRHayes
  1

• Please publish pre-compiled version of uri-js

  #24 opened 6 years ago by ulrivo
  10

• Incorrect resolution with relative paths

  #31 opened 6 years ago by epoberezkin
  1

• Unexpected token during webpack compile after update to 4

  #30 opened 6 years ago by NikkiTheBugSlayer
  6

• Error loading urn.js on IE 11

  #29 opened 6 years ago by dobladov
  1

• Support for earlier versions of node by downgrading dependency on punycode

  #27 opened 6 years ago by ethanherbertson
  5

• 4.2.0 breaks .resolve method for URNs

  #26 opened 6 years ago by epoberezkin
  3

• default value for func parameter(options) is not supported by ie11

  #25 opened 6 years ago by GorbachevA
  1

• Incorrect parsed scheme

  #23 opened 6 years ago by jsumners
  5

• ReferenceError: Unknown plugin "external-helpers"

  #21 opened 7 years ago by chrisg86
  3

• Fails to resolve some URI's that contains \r

  #18 opened 7 years ago by sondrele
  1

• undefined is not an object (evaluating 'URI.SCHEMES')

  #14 opened 7 years ago by mixophrygian
  5

• parse hangs on some long urls

  #12 opened 7 years ago by dotchev
  3

• Error when HOST is a IPv6.

  #13 opened 8 years ago by JonDotsoy
  1

• Path won't be parsed as lower case

  #11 opened 8 years ago by vzaidman
  1

• Uri-js doesn't work in io.js (strict mode)

  #8 opened 9 years ago by teologov
  2

• incorrect parse of url

  #7 opened 9 years ago by codeuniquely
  3

• what is the reason not to place your code in a immediately executed function expression right now it is exposing global variables which are not related to api and you are not defined some of the variables using var

  #6 opened 9 years ago by Prashanth-Nelli
  3

• xip.io hosts parse fail

  #4 opened 10 years ago by terion-name
  1

• IRIs?

  #3 opened 10 years ago by anarchodin
  1