react-toolbox
Version:
A set of complementary tools to ReactJS.
62 lines (39 loc) • 2.67 kB
Markdown
[](https://travis-ci.org/rackt/history)
[](https://www.npmjs.org/package/history)
[ is a JavaScript library that lets you easily manage session history in browsers, testing environments, and (soon, via [React Native](https://facebook.github.io/react-native/)) native devices. `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. `history` is library-agnostic and may easily be included in any JavaScript project.
- [Guides and API Docs](/docs
- [Changelog](/CHANGES.md)
- [
- [Stack Overflow](http://stackoverflow.com/questions/tagged/react-router)
For questions and support, please visit [our channel on Reactiflux](https://discord.gg/0ZcbPKXt5bYaNQ46) or [Stack Overflow](http://stackoverflow.com/questions/tagged/react-router). The issue tracker is *exclusively* for bug reports and feature requests.
Using [npm](https://www.npmjs.org/):
$ npm install history
Then with a module bundler like [webpack](https://webpack.github.io/), use as you would anything else:
```js
// using an ES6 transpiler, like babel
import { createHistory } from 'history'
// not using an ES6 transpiler
var createHistory = require('history').createHistory
```
A "history" encapsulates navigation between different screens in your app, and notifies listeners when the current screen changes.
```js
import { createHistory } from 'history'
let history = createHistory()
// Listen for changes to the current location. The
// listener is called once immediately.
let unlisten = history.listen(location => {
console.log(location.pathname)
})
history.pushState({ the: 'state' }, '/the/path?a=query')
// When you're finished, stop the listener.
unlisten()
```
You can find many more examples [in the documentation](https://github.com/rackt/history/tree/master/docs)!
A big thank-you to [Dan Shaw](https://www.npmjs.com/~dshaw) for letting us use the `history` npm package name! Thanks Dan!
Also, thanks to [BrowserStack](https://www.browserstack.com/) for providing the infrastructure that allows us to run our build in real browsers.