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-cookie-state

v2.1.0

Published

State management React hook using browser cookies as persistent storage

Downloads

3,029

Readme

use-cookie-state

Simple React persistent state management hook, based on browser cookies

NPM

Codecov

Dev.to article on writing this library

Features

  • Persist your state with browser cookies
  • Based on cookie package
  • Supports parse/serialize options
  • Supports Server Side Rendering - behaves like a useState if browser cookies is inaccessible

📦 Installation

with npm
$ npm install --save use-cookie-state cookie
with yarn
$ yarn add use-cookie-state cookie

🕹 API

🔗 useCookieState

Options
  • key - used as cookie name
  • value - initial value, any value or object or function with returns initial hook value
  • options (optional)
    • decode (optional) - cookie parse options
    • encode (optional) - cookie serialize options
Default encode options

If no encode options are passed, the default encode options will be used.

{ path: "/", expires: new Date("9999") }

Otherwise, the passed encode options will be merged with the default encode options.

useCookieState(
  key: string;
  value: any; 
  options?: {
    decode?: cookie.CookieParseOptions, 
    encode?: cookie.CookieSerializeOptions // = { path: "/", expires: new Date("9999") }
  };
)
Returns
  • value - current cookie value
  • setValue - callback to update cookie value
[
  value: T,
  setValue(value: T, encode? cookie.CookieSerializeOptions)
]

📖 Examples

useCookieState behaves like React.useState hook, just put the cookie key as the first argument and the value or function or object or anything else as the second arg. The state will be persistent between rerenders and page reloads. Don't worry about serializing or parsing the state value it just works out of the box!

With simple object and default options

import React from "react";
import { useCookieState } from "use-cookie-state";

function MyComponent() {
  const [state, setState] = useCookieState("mykey", { foo: "bar" })

  return <div>Current state: {state}</div>
}

export default MyComponent

With custom options and function as initial arg

import React from "react";
import { useCookieState } from "use-cookie-state";

const getCookiesInitialValue = () => {
  return "my initial value"
}

function MyComponent() {
  const [state, setState] = useCookieState("mykey", getCookiesInitialValue, {
    encode: {
      httpOnly: true,
      maxAge: 60 * 60 * 24 * 7 // 1 week
    }
  })

  const handleUpdate = () => {
    setState(
      "next cookie value", 
      { encode: { domain: "example.com"} } // update value fn also accepts custom encode options
    )
  }

  return (
    <div>
      <div>Current state: {state}</div>
      <button onClick={handleUpdate}>Update current state</button>
    </div>
  )
}

export default MyComponent

License

MIT © dqunbp