
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
history
is a JavaScript library that lets you easily manage session history anywhere JavaScript runs. history
abstracts away the differences in various environments and provides a minimal API that lets you manage the history stack, navigate, confirm navigation, and persist state between sessions.
Using npm:
$ npm install --save vhistory
Then with a module bundler like webpack, use as you would anything else:
// using an ES6 transpiler, like babel
import { createHistory } from 'vhistory'
// not using an ES6 transpiler
var createHistory = require('vhistory').createHistory
The UMD build is also available on unpkg:
<script src="https://unpkg.com/history/umd/history.min.js"></script>
You can find the library on window.History
.
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()
// Get the current location
const location = history.getCurrentLocation()
// Listen for changes to the current location
const unlisten = history.listen(location => {
console.log(location.pathname)
})
// Push a new entry onto the history stack
history.push({
pathname: '/the/path',
search: '?a=query',
// Extra location-specific state may be kept in session
// storage instead of in the URL query string!
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.
FAQs
Manage browser history with JavaScript
The npm package vhistory receives a total of 13 weekly downloads. As such, vhistory popularity was classified as not popular.
We found that vhistory demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.