npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

normalizeurl

v1.0.0

Published

Normalize a url or url fragment by percent-encoding exactly the chars encodeURIComponent does

Downloads

54,275

Readme

normalizeurl

Normalize a url or url fragment by percent-encoding exactly the chars encodeURIComponent does and removing /./ and /foo/../ constructs like require('path').resolve does.

Example:

var normalizeUrl = require('normalizeurl');

console.log(normalizeUrl('http://example.com/%7efoo%2Ebar'));
// => 'http://example.com/~foo.bar'

console.log(normalizeUrl('http://example.com/foo/./bar/quux/../blah'));
// => 'http://example.com/foo/bar/blah'

It also does the right thing for relative, root-relative, and protocol-relative urls:

console.log(normalizeUrl('foo/bar/../blah'));
// => 'foo/bar/blah'

console.log(normalizeUrl('/hey/there/../you?blah?#foo%7e'));
// => '/hey/you?blah?#foo~'

console.log(normalizeUrl('//example.com/%7efoo'));
// => '//example.com/~foo'

Url objects already parsed by node.js' built-in url module are also supported:

console.log(normalizeUrl(require('url').parse('htTP://foo.com/%7ebarf')));
// => {protocol: 'http:', slashes: true, host: 'foo.com', hostname: 'foo.com', pathname: '/~barf', href: 'http://foo.com/~barf', path: '/~barf'}

The module works also works in a browser, but only for url fragments for now. It'll throw an exception if you attempt to normalize an absolute or protocol-relative url, as that currently relies on require('url').parse.

License

normalizeurl is licensed under a standard 3-clause BSD license -- see the LICENSE-file for details.