vue-context-storage
v0.1.27
Published
Vue 3 context storage system with URL query synchronization support
Readme
vue-context-storage
Vue 3 context storage system with URL query, localStorage, and sessionStorage synchronization support.
A powerful state management solution for Vue 3 applications that provides:
- Context-based storage using Vue's provide/inject API
- Automatic URL query synchronization for preserving state across page reloads
- localStorage & sessionStorage handlers for persistent and session-scoped state
- Multiple storage contexts with activation management
- Type-safe TypeScript support
- Tree-shakeable and lightweight
Live Demo
🚀 Try the interactive playground
Installation
npm install vue-context-storageFeatures
- ✅ Vue 3 Composition API - Built with modern Vue patterns
- ✅ URL Query Sync - Automatically sync state with URL parameters
- ✅ localStorage Handler - Persist state to localStorage with cross-tab sync
- ✅ sessionStorage Handler - Session-scoped state that survives page refreshes
- ✅ Multiple Contexts - Support multiple independent storage contexts
- ✅ TypeScript - Full type safety and IntelliSense support
- ✅ Flexible - Works with vue-router 4+ or 5+
- ✅ Transform Helpers - Built-in utilities for type conversion
Motivation
In Vue applications, reactive state often needs to live beyond a single component. Filters, pagination, sorting, and user preferences must survive page reloads, be shareable via URL, or persist across sessions. Solving this typically means writing the same boilerplate over and over: manually reading and writing query parameters with vue-router, serializing objects to localStorage, handling type coercion from URL strings, and keeping everything in sync.
vue-context-storage eliminates that repetitive work. You declare your reactive state once, point it at a storage target, and the library handles the rest:
- URL query parameters stay in sync with your data automatically -- users can bookmark or share a page and get the exact same state back.
- localStorage and sessionStorage are kept up to date without manual
getItem/setItemcalls, including cross-tab synchronization. - Type safety is preserved end-to-end: URL strings are coerced back to numbers, booleans, and arrays via transform helpers or Zod schemas.
- Multiple independent contexts (e.g. two data tables on the same page) are supported out of the box through the prefix pattern, so query parameters never collide.
The goal is a single, declarative API -- useContextStorage('query', data, options) -- that replaces scattered watchers, router guards, and storage listeners with one composable call per piece of state.
Basic Usage
Option 1: Manual Component Import (Recommended)
Import ContextStorage component in your App.vue:
<template>
<ContextStorage>
<router-view />
</ContextStorage>
</template>
<script setup lang="ts">
import { ContextStorage } from 'vue-context-storage/components'
</script>Option 2: Using Vue Plugin
Register the plugin in your main app file:
import { createApp } from 'vue'
import { VueContextStoragePlugin } from 'vue-context-storage/plugin'
import App from './App.vue'
const app = createApp(App)
// Register components globally
app.use(VueContextStoragePlugin)
app.mount('#app')Then use components without importing in your App.vue:
<template>
<ContextStorage>
<router-view />
</ContextStorage>
</template>Unified Composable
useContextStorage() provides a single entry point for all handler types:
<script setup lang="ts">
import { reactive } from 'vue'
import { useContextStorage } from 'vue-context-storage'
const filters = reactive({
search: '',
status: 'active',
page: 1,
})
// Sync with URL query
useContextStorage('query', filters, {
prefix: 'filters',
})
// Sync with localStorage
useContextStorage('localStorage', filters, {
key: 'saved-filters',
})
// Sync with sessionStorage
useContextStorage('sessionStorage', filters, {
key: 'temp-filters',
})
</script>Options are type-checked per handler — 'query' accepts query options, 'localStorage' and 'sessionStorage' require a key, etc.
You can also pass an injection key directly instead of a string:
import { contextStorageQueryHandlerInjectKey } from 'vue-context-storage'
useContextStorage(contextStorageQueryHandlerInjectKey, filters, {
prefix: 'filters',
})Registering Custom Handlers
Register your own handlers at runtime and extend the type map for full type safety:
import { defineContextStorageHandler } from 'vue-context-storage'
import { myHandlerInjectionKey } from './my-handler'
// Runtime registration
defineContextStorageHandler('myHandler', myHandlerInjectionKey)
// TypeScript augmentation (e.g. in a .d.ts or at module level)
declare module 'vue-context-storage' {
interface ContextStorageHandlerMap {
myHandler: { key: string }
}
}
// Now fully type-checked
useContextStorage('myHandler', data, { key: 'example' })Prefix Scoping with <ContextStoragePrefix>
The <ContextStoragePrefix> component adds a prefix to all useContextStorage calls within its subtree. Prefixes stack when nested, and are concatenated with bracket notation.
Basic Usage
<template>
<ContextStoragePrefix name="table">
<MyTable />
</ContextStoragePrefix>
</template>Inside MyTable, any useContextStorage('query', data) call will automatically get prefix: 'tables'. If the composable also specifies its own prefix, they are combined:
// Inside MyTable — effective prefix becomes 'table[filters]'
useContextStorage('query', filters, { prefix: 'filters' })
// URL: ?table[filters][search]=...Stacking Prefixes
Nested <ContextStoragePrefix> components stack their prefixes:
<ContextStoragePrefix name="tables">
<ContextStoragePrefix name="first">
<!-- All handlers here get prefix 'tables[first]' -->
<!-- useContextStorage('query', data) → URL: ?tables[first][search]=... -->
<!-- useContextStorage('localStorage', data, { key: 'state' }) → key: 'state[tables][first]' -->
</ContextStoragePrefix>
</ContextStoragePrefix>Per-Handler Prefixes
Pass an object to apply different prefixes per handler type:
<ContextStoragePrefix :name="{ query: 'url-tables', localStorage: 'ls-data' }">
<!-- query handler gets prefix 'url-tables' -->
<!-- localStorage handler gets prefix 'ls-data' -->
<!-- sessionStorage handler gets no prefix (not specified) -->
</ContextStoragePrefix>Dynamic Prefix
When the name prop changes, all descendant components are re-created and re-registered with the new prefix:
<ContextStoragePrefix :name="activeTab">
<TabContent />
</ContextStoragePrefix>Use Query Handler in Components
Sync reactive state with URL query parameters:
<script setup lang="ts">
import { reactive } from 'vue'
import { useContextStorage } from 'vue-context-storage'
interface Filters {
search: string
status: string
page: number
}
const filters = reactive<Filters>({
search: '',
status: 'active',
page: 1,
})
// Automatically syncs filters with URL query
useContextStorage('query', filters, {
prefix: 'filters', // URL will be: ?filters[search]=...&filters[status]=...
})
</script>Also available as a dedicated composable:
import { useContextStorageQueryHandler } from 'vue-context-storage'
useContextStorageQueryHandler(filters, {
prefix: 'filters',
})Advanced Usage
Using Transform Helpers
Convert URL query string values to proper types:
import { ref } from 'vue'
import { useContextStorage, transform } from 'vue-context-storage'
interface TableState {
page: number
search: string
perPage: number
}
const state = ref<TableState>({
page: 1,
search: '',
perPage: 25,
})
useContextStorage('query', state, {
prefix: 'table',
transform: (deserialized, initial) => ({
page: transform.asNumber(deserialized.page, { fallback: 1 }),
search: transform.asString(deserialized.search, { fallback: '' }),
perPage: transform.asNumber(deserialized.perPage, { fallback: 25 }),
}),
})Available Transform Helpers
asNumber(value, options)- Convert to numberasString(value, options)- Convert to stringasBoolean(value, options)- Convert to booleanasArray(value, options)- Convert to arrayasNumberArray(value, options)- Convert to number array
Using Zod Schemas
Alternatively, you can use Zod schemas for automatic validation and type inference:
import { z } from 'zod'
import { useContextStorage } from 'vue-context-storage'
// Define schema with automatic coercion
const FiltersSchema = z.object({
search: z.string().default(''),
page: z.coerce.number().int().positive().default(1),
status: z.enum(['active', 'inactive']).default('active'),
})
const filters = ref(FiltersSchema.parse({}))
// Use schema for automatic validation
useContextStorage('query', filters, {
prefix: 'filters',
schema: FiltersSchema,
})Benefits:
- Automatic type coercion (strings → numbers, etc.)
- Runtime validation with detailed errors
- Automatic TypeScript type inference
- Less boilerplate code
- Single source of truth for structure and validation
Preserve Empty State
Keep empty state in URL to prevent resetting on reload:
useContextStorage('query', filters, {
prefix: 'filters',
preserveEmptyState: true,
// Empty filters will show as: ?filters
// Without this option, empty filters would clear the URL completely
})Configure Query Handler
Customize global behavior:
import { ContextStorageQueryHandler } from 'vue-context-storage'
ContextStorageQueryHandler.configure({
mode: 'push', // 'replace' (default) or 'push' for history
preserveUnusedKeys: true, // Keep other query params
preserveEmptyState: false,
})Use localStorage Handler in Components
Persist reactive state to localStorage. Data is automatically synced across browser tabs.
<script setup lang="ts">
import { reactive } from 'vue'
import { useContextStorage } from 'vue-context-storage'
const settings = reactive({
theme: 'light',
fontSize: 14,
sidebarOpen: true,
})
// Automatically syncs settings with localStorage under the key "app-settings"
useContextStorage('localStorage', settings, {
key: 'app-settings',
})
</script>Also available as a dedicated composable:
import { useContextStorageLocalStorage } from 'vue-context-storage'
useContextStorageLocalStorage(settings, {
key: 'app-settings',
})Configure localStorage Handler
import { ContextStorageLocalStorageHandler } from 'vue-context-storage'
ContextStorageLocalStorageHandler.configure({
listenToStorageEvents: true, // Cross-tab sync (default: true)
})Use sessionStorage Handler in Components
Persist reactive state to sessionStorage. Data survives page refreshes but is cleared when the tab is closed.
<script setup lang="ts">
import { reactive } from 'vue'
import { useContextStorage } from 'vue-context-storage'
const formDraft = reactive({
email: '',
message: '',
step: 1,
})
// Automatically syncs form draft with sessionStorage
useContextStorage('sessionStorage', formDraft, {
key: 'contact-form-draft',
})
</script>Also available as a dedicated composable:
import { useContextStorageSessionStorage } from 'vue-context-storage'
useContextStorageSessionStorage(formDraft, {
key: 'contact-form-draft',
})Using Prefix
The prefix is appended to the storage key in bracket notation, so each prefixed registration gets its own storage entry:
const filters = reactive({ search: '', status: 'active' })
useContextStorage('sessionStorage', filters, {
key: 'app-state',
prefix: 'filters', // Storage key: 'app-state[filters]', value: { search: '', status: 'active' }
})
const pagination = reactive({ page: 1, perPage: 25 })
useContextStorage('sessionStorage', pagination, {
key: 'app-state',
prefix: 'pagination', // Storage key: 'app-state[pagination]', value: { page: 1, perPage: 25 }
})Using Transform with Storage Handlers
Convert stored values to proper types when reading from storage:
import { useContextStorage, transform } from 'vue-context-storage'
const settings = reactive({
theme: 'light',
fontSize: 14,
})
useContextStorage('localStorage', settings, {
key: 'app-settings',
transform: (deserialized, initial) => ({
theme: transform.asString(deserialized.theme, { fallback: 'light' }),
fontSize: transform.asNumber(deserialized.fontSize, { fallback: 14 }),
}),
})Using Zod Schemas with Storage Handlers
import { z } from 'zod'
import { useContextStorageLocalStorage } from 'vue-context-storage'
const SettingsSchema = z.object({
theme: z.enum(['light', 'dark']).default('light'),
fontSize: z.number().int().positive().default(14),
sidebarOpen: z.boolean().default(true),
})
const settings = reactive(SettingsSchema.parse({}))
useContextStorage('localStorage', settings, {
key: 'app-settings',
schema: SettingsSchema,
})Custom Serialization
Provide custom serializer/deserializer functions:
useContextStorage('localStorage', settings, {
key: 'app-settings',
serializer: (data) => btoa(JSON.stringify(data)),
deserializer: (str) => JSON.parse(atob(str)),
})API Reference
Composables
useContextStorage(type, data, options)
Unified composable that delegates to the correct handler based on type.
Parameters:
type: 'query' | 'localStorage' | 'sessionStorage' | InjectionKey- Handler type or injection keydata: MaybeRefOrGetter<T>- Reactive reference to syncoptions- Handler-specific options (type-checked per handler)
Returns: { data, stop, reset, wasChanged }
data- The reactive reference passed instop()- Unregister and stop syncing (called automatically on unmount)reset()- Restore data to its initial statewasChanged: ComputedRef<boolean>- Whether data differs from initial state
Custom handler registration:
defineContextStorageHandler(name, injectionKey)- Register a custom handlerresolveHandlerInjectionKey(type)- Look up an injection key by name
useContextStorageQueryHandler<T>(data, options)
Registers reactive data for URL query synchronization.
Parameters:
data: MaybeRefOrGetter<T>- Reactive reference to syncoptions?: RegisterQueryHandlerOptions<T>prefix?: string- Query parameter prefixtransform?: (deserialized, initial) => T- Transform functionpreserveEmptyState?: boolean- Keep empty state in URLmergeOnlyExistingKeysWithoutTransform?: boolean- Only merge existing keys (default: true)
Classes
ContextStorageQueryHandler
Main handler for URL query synchronization.
Static Methods:
configure(options): ContextStorageHandlerConstructor- Configure global optionsgetInitialStateResolver(): () => LocationQuery- Get initial state resolver
Methods:
register<T>(data, options): () => void- Register data for syncsetEnabled(state, initial): void- Enable/disable handlersetInitialState(state): void- Set initial state
useContextStorageLocalStorage<T>(data, options)
Registers reactive data for localStorage synchronization.
Parameters:
data: MaybeRefOrGetter<T>- Reactive reference to syncoptions: RegisterWebStorageHandlerBaseOptions<T>key: string- Storage key (required)prefix?: string- Appended to the storage key in bracket notation (e.g. key'app'+ prefix'filters'= storage key'app[filters]')transform?: (deserialized, initial) => T- Transform functionschema?: ZodSchema- Zod schema for validationserializer?: (data: T) => string- Custom serializer (default:JSON.stringify)deserializer?: (str: string) => unknown- Custom deserializer (default:JSON.parse)
useContextStorageSessionStorage<T>(data, options)
Registers reactive data for sessionStorage synchronization. Same options as useContextStorageLocalStorage.
Classes
ContextStorageLocalStorageHandler
Handler for localStorage synchronization. Supports cross-tab sync via storage events.
Static Methods:
configure(options): ContextStorageHandlerConstructor- Configure global optionslistenToStorageEvents?: boolean- Enable cross-tab sync (default:true)
ContextStorageSessionStorageHandler
Handler for sessionStorage synchronization. Data is scoped to the current tab.
Static Methods:
configure(options): ContextStorageHandlerConstructor- Configure global optionslistenToStorageEvents?: boolean- Listen to storage events (default:false)
Components
<ContextStoragePrefix>
Scopes a prefix for all descendant useContextStorage calls via provide/inject.
Props:
name: string | Partial<Record<string, string>>(required) - Prefix to apply. A string applies to all handlers; an object applies per handler type (e.g.{ query: 'q', localStorage: 'ls' })
Nested <ContextStoragePrefix> components stack their prefixes using bracket notation. When name changes dynamically, all descendant components are re-created.
Transform Helpers
All transform helpers support nullable and missable options:
transform.asNumber(value, {
fallback: 0, // Default value
nullable: false, // Allow null return
missable: false, // Allow undefined return
})TypeScript Support
Full TypeScript support with type inference:
import type {
ContextStorageHandler,
ContextStorageHandlerConstructor,
IContextStorageQueryHandler,
QueryValue,
SerializeOptions,
} from 'vue-context-storage'When using Zod schemas, TypeScript will automatically infer types:
const FiltersSchema = z.object({
search: z.string().default(''),
page: z.coerce.number().default(1),
})
type Filters = z.infer<typeof FiltersSchema>
// Result: { search: string; page: number }Examples
Pagination with URL Sync
import { ref } from 'vue'
import { useContextStorageQueryHandler, transform } from 'vue-context-storage'
const pagination = ref({
page: 1,
perPage: 25,
total: 0,
})
useContextStorageQueryHandler(pagination, {
prefix: 'page',
transform: (data, initial) => ({
page: transform.asNumber(data.page, { fallback: 1 }),
perPage: transform.asNumber(data.perPage, { fallback: 25 }),
total: initial.total, // Don't sync total from URL
}),
})Peer Dependencies
vue: ^3.0.0vue-router: ^4.0.0 || ^5.0.0zod: ^4.0.0 (optional - only if using schema validation)
License
MIT
Development
Running Playground Locally
# Development mode (hot reload)
npm run play
# Production preview
npm run build:playground
npm run preview:playgroundBuilding
# Build library
npm run build
# Build playground for deployment
npm run build:playgroundTesting & Quality
# Run all checks
npm run check
# Type checking
npm run ts:check
# Linting
npm run lint
# Formatting
npm run formatContributing
Contributions are welcome! Please feel free to submit a Pull Request.
