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

parse-link

v1.0.3

Published

Unified URL parsing API in the browser and node

Downloads

51

Readme

parse-link

Build Coverage Downloads Size

Unified URL parsing API in the browser and Node.

Installation

npm:

npm install parse-link

Usage

var parse = require('parse-link')

console.log(parse('http://user:[email protected]:8080/path?query=string#hash'))

Yields:

{
  protocol: 'http:',
  host: 'host.com:8080',
  port: 8080,
  hostname: 'host.com',
  hash: '#hash',
  search: '?query=string',
  query: 'query=string',
  pathname: '/path',
  href: 'http://user:[email protected]:8080/path?query=string#hash' }

Node also supports some more properties, like path ("/path?query=string") and auth ("user:pass").

API

parse(url)

Parses url (string). Uses anchor tags in the browser, and Node’s URL module in Node.

Returns

Object:

  • href (string) — given (cleaned) url
  • pathname (string) — path
  • protocol (string) — http:, https:, mailto:, etc
  • hostname (string) — complete domain, including subdomains and www.
  • host (string) — hostname with port
  • port (number) — TCP port
  • search (string) — query with question mark
  • query (string) — GET parameters
  • hash (string) — Hash, including pound/octothorp/what-evs

Node supports a second parameter which the given url is relative to: In the browser, URLs are parsed relative to window.location, whereas in Node such a thing doesn’t exist.

Todo

There are still some slight differences between the two interfaces: mostly in non-http settings, or with relative links. I’d like to make them look more alike.

License

MIT © Titus Wormer