React hook that persists data in sessionStorage
Installations
npm install use-session-storage-state
Score
74.7
Supply Chain
93.1
Quality
82.1
Maintenance
100
Vulnerability
100
License
Developer
astoilkov
Developer Guide
Module System
ESM
Min. Node Version
>=14
Typescript Support
No
Node Version
NPM Version
Statistics
21 Stars
29 Commits
2 Watching
2 Branches
1 Contributors
Updated on 04 Nov 2024
Bundle Size
1.66 kB
Minified
780.00 B
Minified + Gzipped
Languages
TypeScript (98.01%)
JavaScript (1.99%)
Total Downloads
Cumulative downloads
Total Downloads
518,280
Last day
-27.9%
1,184
Compared to previous day
Last week
-12.8%
6,787
Compared to previous week
Last month
18.1%
32,454
Compared to previous month
Last year
64%
316,483
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
25
use-session-storage-state
React hook that persist data in
sessionStorage
Install
React 18 and above:
1npm install use-session-storage-state
⚠️ React 17 and below. For docs, go to the react-17 branch.
1npm install use-session-storage-state@17
Why
- Clone of
use-local-storage-state
that I've been actively maintaining for the past 4 years. - SSR support.
- Works with concurrent rendering and React 19.
- Handles the
Window
storage
event and updates changes across iframe's. Disable withstorageSync: false
. - In-memory fallback when
sessionStorage
throws an error and can't store the data. Provides aisPersistent
API to let you notify the user their data isn't currently being stored. - Aiming for high-quality with my open-source principles.
Usage
1import useSessionStorageState from 'use-session-storage-state' 2 3export default function Todos() { 4 const [todos, setTodos] = useSessionStorageState('todos', { 5 defaultValue: ['buy avocado', 'do 50 push-ups'] 6 }) 7}
Todo list example
1import React, { useState } from 'react' 2import useSessionStorageState from 'use-session-storage-state' 3 4export default function Todos() { 5 const [todos, setTodos] = useSessionStorageState('todos', { 6 defaultValue: ['buy avocado'] 7 }) 8 const [query, setQuery] = useState('') 9 10 function onClick() { 11 setQuery('') 12 setTodos([...todos, query]) 13 } 14 15 return ( 16 <> 17 <input value={query} onChange={e => setQuery(e.target.value)} /> 18 <button onClick={onClick}>Create</button> 19 {todos.map(todo => ( 20 <div>{todo}</div> 21 ))} 22 </> 23 ) 24} 25
Notify the user when sessionStorage
isn't saving the data using the isPersistent
property
There are a few cases when sessionStorage
isn't available. The isPersistent
property tells you if the data is persisted in sessionStorage
or in-memory. Useful when you want to notify the user that their data won't be persisted.
1import React, { useState } from 'react' 2import useSessionStorageState from 'use-session-storage-state' 3 4export default function Todos() { 5 const [todos, setTodos, { isPersistent }] = useSessionStorageState('todos', { 6 defaultValue: ['buy avocado'] 7 }) 8 9 return ( 10 <> 11 {todos.map(todo => (<div>{todo}</div>))} 12 {!isPersistent && <span>Changes aren't currently persisted.</span>} 13 </> 14 ) 15} 16
Removing the data from sessionStorage
and resetting to the default
The removeItem()
method will reset the value to its default and will remove the key from the sessionStorage
. It returns to the same state as when the hook was initially created.
1import useSessionStorageState from 'use-session-storage-state' 2 3export default function Todos() { 4 const [todos, setTodos, { removeItem }] = useSessionStorageState('todos', { 5 defaultValue: ['buy avocado'] 6 }) 7 8 function onClick() { 9 removeItem() 10 } 11}
Why does my component re-renders twice?
If you are hydrating your component (for example, if you are using Next.js), your component might re-render twice. This is behavior specific to React and not to this library. It's caused by the useSyncExternalStore()
hook. There is no workaround. This has been discussed in the issues: https://github.com/astoilkov/use-local-storage-state/issues/56.
If you want to know if you are currently rendering the server value you can use this helper function:
1function useIsServerRender() { 2 return useSyncExternalStore(() => { 3 return () => {} 4 }, () => false, () => true) 5}
API
useSessionStorageState(key: string, options?: SessionStorageOptions)
Returns [value, setValue, { removeItem, isPersistent }]
when called. The first two values are the same as useState()
. The third value contains two extra properties:
removeItem()
— callssessionStorage.removeItem(key)
and resets the hook to it's default stateisPersistent
—boolean
property that returnsfalse
ifsessionStorage
is throwing an error and the data is stored only in-memory
key
Type: string
The key used when calling sessionStorage.setItem(key)
and sessionStorage.getItem(key)
.
⚠️ Be careful with name conflicts as it is possible to access a property which is already in sessionStorage
that was created from another place in the codebase or in an old version of the application.
options.defaultValue
Type: any
Default: undefined
The default value. You can think of it as the same as useState(defaultValue)
.
options.storageSync
Type: boolean
Default: true
Setting to false
doesn't subscribe to the Window storage event. If you set to false
, updates won't be synchronized across iframes.
Note: Unlike localStorage
, sessionStorage
doesn't fire the storage
event across tabs and windows.
options.serializer
Type: { stringify, parse }
Default: JSON
JSON does not serialize Date
, Regex
, or BigInt
data. You can pass in superjson or other JSON
-compatible serialization library for more advanced serialization.
Related
use-storage-state
— SupportslocalStorage
,sessionStorage
, and any otherStorage
compatible API.use-local-storage-state
— A clone of this library but forlocalStorage
.use-db
— Similar to this hook but forIndexedDB
.local-db-storage
— Tiny wrapper aroundIndexedDB
that mimicslocalStorage
API.
No vulnerabilities found.
No security vulnerabilities found.