Minimalist History API abstraction for building URL driven browser applications.
So your website feels like a native app but still has cool URLs. Or URIs, or whatever...
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()
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.
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.
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
Sugar for url.push(href, true)
.
Equivalent to window.history.back()
Update window.location.search
without clobbering the existing query. Set keys to null
to remove them.
params
Object
Read only. These properties are described in the URL spec.
Read only. True during the first history change and any nested changes.
Read only. True when the browser's back button has been clicked or url.pop()
was called.
Read only. A parsed search (query) string object.
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.
$ npm run test
MIT