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

use-history-state

v0.1.5

Published

`use-history-state` is replacement for `useState` that stores the state within the history state.

Downloads

35

Readme

useHistoryState

useHistoryState is replacement for useState that stores the state within the history state.

The difference between useHistoryState and useState is that every changes in your state will be stored within the navigator history. And so, if you go back in your history, you will change the inner value of the state.

How to use

import React, { Fragment } from "react";
import useHistoryState from "use-history-state";

const Component = () => {
  // const [state, setState] = useHistoryState(initialValue, keyInHistoryState);
  const [name, setName] = useHistoryState("", "name");

  const names = ["John", "Susan", "Hugo", "Jade", "Mike", "Aurora"];

  return (
    <Fragment>
      <h1>{name}</h1>
      {names.map(n => (
        <button key={n} type="button" onClick={() => setName(n)} />
      ))}
    </Fragment>
  );
};

useHistoryState

function useHistoryState<State>(initialValue: State | () => State, key: string) {}

If there is already the specified key within the history's state, the initial value will be set to this value. Otherwise, it will you initialValue set as argument.

setState

function setState<State>(newState: State | State => void, replace?: boolean) {}

When you use the setState function, you can specify a second argument: replace.

  • If replace is set to true, under the hood setState will use history.replaceState and so, if you want to go back to the previous page, you won't reach the replaced states.
  • If replace is set to false, under the hood setState will use history.pushState, which means that every changes will be available in you history.

By default, replace is set to false

Installation

npm

npm i --save use-history-state
import useHistoryState from "use-history-state"; // esm
const useHistoryState = require("use-history-state"); // cjs

yarn

yarn add use-history-state
import useHistoryState from "use-history-state"; // esm
const useHistoryState = require("use-history-state"); // cjs

umd

<script src="https://unpkg.com/[email protected]/dist/useHistoryState.umd.js">
const useHistoryState = window["use-history-state"];