history abstracts away the differences in these different platforms and provides a minimal API that lets you manage the history stack, navigate, confirm navigation, and persist state between sessions.
$ npm install --save history
Then with a module bundler like webpack, use as you would anything else:
// using an ES6 transpiler, like babelimport createHistory from 'history'// not using an ES6 transpilervar createHistory = require'history'createHistory
The UMD build is also available on npmcdn:
You can find the library on
A "history" encapsulates navigation between different screens in your app, and notifies listeners when the current screen changes.
import createHistory from 'history'const history = createHistory// Listen for changes to the current location. The// listener is called once immediately.const unlisten = historylistenlocation =>console.loglocationpathnamehistorypushpathname: '/the/path'search: '?a=query'state: the: 'state'// When you're finished, stop the listener.unlisten
You can find many more examples in the documentation!
A big thank-you to Dan Shaw for letting us use the
history npm package name! Thanks Dan!
Also, thanks to BrowserStack for providing the infrastructure that allows us to run our build in real browsers.