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 🙏

© 2025 – Pkg Stats / Ryan Hefner

parse-url-parts

v2.0.3

Published

Parse parts of uniform resource locators

Readme

parse-url-parts

npm npm bundle size

A lightweight JavaScript library for parsing RFC 1738 compliant Uniform Resource Locators (URLs).

Description

Parses any RFC 1738 compliant url, including localhost and ftp urls.

The above Syntax diagram from Wikipedia visualizes the supported structure of urls for this module.

Documentation

parseUrlParts(url)

Parses parts of an url.

Note: If a non-valid url is passed, it will return null.

Note: Urls need to have at least a protocol and a host part

Params

  • String url: The url to be parsed.

Return

  • Object An object containing the following fields:
  • protocol (String): The protocol.
  • username (null|String): The username of urls with userinfo (e.g. FTP urls).
  • password (null|String): The password of urls with userinfo (e.g. FTP urls).
  • host (String): Full host (subDomains + rootDomain + topLevelDomain).
  • subDomains (null|String): Comma-separated list of subDomains
  • rootDomain (String): The rootDomain of the url.
  • topLevelDomain (null|String): The topLevelDomain of the url.
  • port (null|Number): The port of the url.
  • path (String): Full path of the url, without query params of fragment.
  • queryParams (null|String): Query parameters of the url.
  • fragment (null|String): Fragment of the url, without leading "#".

Usage

import { parseUrlParts } from "parse-url-parts"

const url = "https://foo:[email protected]:80/path/deeper-path?q=amazingQuery#id"

console.log(parseUrlParts(url))
// { protocol: 'https',
//   username: 'foo',
//   password: 'bar',
//   host: 'www.example.com',
//   subDomains: 'www',
//   rootDomain: 'example',
//   topLevelDomain: 'com',
//   port: 80,
//   path: '/path/deeper-path',
//   queryParams: 'q=amazingquery',
//   fragment: 'id' }

If any non-required part is not found, its value will be null:

import { parseUrlParts } from "parse-url-parts"

const url = "https://example.com"

console.log(parseUrlParts(url))
// { protocol: 'https',
//   username: null,
//   password: null,
//   host: 'example.com',
//   subDomains: null,
//   rootDomain: 'example',
//   topLevelDomain: 'com',
//   port: null,
//   path: "",
//   queryParams: null,
//   fragment: null }

Contributing

GitHub contributors

Contributions and/or critics are welcome! Just open pull requests and issues on things that matter to you!

Testing

$ npm run jest