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

@offirmo/simple-querystring-parser

v1.1.0

Published

A trivial, low footprint, no dependency, url querystring parser for the browser including typescript typings

Downloads

12

Readme

simple-querystring-parser

A trivial, low footprint, no dependency, UMD-compatible url querystring parser for the browser including typescript typings

This version departs from the venerable https://github.com/sindresorhus/query-string on those points:

  • only 75 lines, no dependencies, ES5
  • parses only (lighter)
  • attempts to do a light type inference from the values (number, boolean)
  • interprets "no value" as true (boolean) XXX this is non-standard but we consider it better (i.e. interpreting it as a flag)
  • typescript compatible
  • UMD compatible, but also exposes itself as a global var, even when loaded by a module loader. Reason: this lib may be needed by low-level code, for ex. a "verbose" option activating logs should be detected very early, maybe from inline code without a loader.

Tested in latest Chrome, FF and Safari and PhantomJS versions.

Usage

yarn add @offirmo/simple-querystring-parser
npm install --save @offirmo/simple-querystring-parser

Base, 99% of the time:

import * as SimpleQuerystringParser from '@offirmo/simple-querystring-parser'

const options = SimpleQuerystringParser.parse(window.location.search)

The type inference covers only the most useful cases:

  • trivial positive integers will be converted to numbers
  • true/false will be converted to boolean (case SENSITIVE)
  • nothing "" will be converted to true (boolean)

This lib DOES NOT parse arrays, for the same reasons exposed by @sindresorhus you should better use json directly.

Rare stuff:

If you don't like the type inference or want to extend it / write your own:

import * as SimpleQuerystringParser from '@offirmo/simple-querystring-parser'

SimpleQuerystringParser.parse(location.params, {
	valueDecoder: value => value
})

// just in case, the value decoder is exposed:
SimpleQuerystringParser.lightQuerystringValueDecoder('foo')

hat tips

  • UMD block inspired from https://github.com/umdjs/umd/blob/master/templates/returnExportsGlobal.js
  • borrowed some ideas from https://github.com/sindresorhus/query-string
  • borrowed some ideas from colleagues

License

The UNLICENSE

CONTRIBUTING

Very simple. Some crappy unit tests. Try to keep the design principles.