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

url-state

v5.0.3

Published

Minimalist history API abstraction for building URL driven browser applications

Downloads

421

Readme

url-state

Minimalist History API abstraction for building URL driven browser applications.

Why

So your website feels like a native app but still has cool URLs. Or URIs, or whatever...

How

import url from 'url-state'

url.addEventListener('change', () => {
  console.log(url.pathname, url.params)
})

url.push('/pathnames')
url.pop()
url.push('#hashes')
url.pop()
url.push('?query=strings')
url.query({ query: 'objects' }, true)
url.query({ query: null }, true)
url.pop()

API

import url from 'url-state'

Returns a UrlState singleton. The first time url-state is imported, it will globally hijack all link clicks and form submissions targeting the origin and begin listening for the popstate event.

Methods

To get proper event sequencing, it's critical you do not use window.history.{pushState,replaceState,go,forward,back}() directly. Use the methods below instead.

url.push([href][, replace])

Equivalent to window.history.go(href). If href is ommited this is equivalent to window.history.forward()

  • href String|Object{pathname,query,hash,replace}
  • replace Boolean; indicates to use replaceState instead of pushState

url.replace(href)

Sugar for url.push(href, true).

url.pop()

Equivalent to window.history.back()

url.query(params[, replace])

Update window.location.search without clobbering the existing query. Set keys to null to remove them.

  • params Object

Properties

href protocol hostname port pathname search hash host origin

Read only. These properties are described in the URL spec.

init

Read only. True during the first history change and any nested changes.

back

Read only. True when the browser's back button has been clicked or url.pop() was called.

params

Read only. A parsed search (query) string object.

virtual

Read/write. When true, window.history is not manipulated. Push/replace/query methods function normally but back and forward (pop, push with no args) are disallowed. The default value is initialized to be true when running in a frame or progressive web app context but may be changed at any time.

Test

$ npm run test

License

MIT