@rnw-community/lock-decorator
v2.15.0
Published
Framework-agnostic sequential and exclusive method lock decorators. Dual ESM+CJS. Built on TypeScript's experimentalDecorators.
Maintainers
Readme
Lock Decorator
Framework-agnostic sequential and exclusive method lock decorators. Promise and Observable return shapes both supported. TypeScript experimentalDecorators. Dual ESM + CJS. rxjs is an optional peer — required only when using the $-suffixed Observable factories or createLockMiddleware$.
The four decorator factories
| | Promise-returning methods | Observable-returning methods |
|---|---|---|
| Sequential (FIFO queue on key) | createSequentialLockDecorator | createSequentialLockDecorator$ |
| Exclusive (skip-on-busy) | createExclusiveLockDecorator | createExclusiveLockDecorator$ |
Each factory takes { store }: CreateLockOptionsInterface and returns a decorator factory that accepts the same key argument shape (string, (args) => string, or { key, timeoutMs?, signal? } for sequential; { key } only for exclusive — exclusive does not wait, so timeout/signal make no sense).
"FIFO queue" and "skip-on-busy" are the semantics a LockStoreInterface implementation is expected to provide — the decorators/middleware only resolve the key and forward mode, key, and options (timeoutMs/signal) to store.acquire(), then propagate whatever it resolves or rejects with. See "Store contract" and "Errors" below for exactly what the library itself does vs. what the store owns.
Sequential (Promise)
createSequentialLockDecorator
Forwards timeoutMs and signal to store.acquire() as part of AcquireOptionsInterface — a compliant store queues on the key (FIFO) and rejects with LockAcquireTimeoutError if timeoutMs elapses, or honors the AbortSignal itself. The decorator does not enforce either behavior; it only awaits store.acquire() and propagates whatever it resolves or rejects with.
import { createSequentialLockDecorator } from '@rnw-community/lock-decorator';
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
declare const store: LockStoreInterface;
const SequentialLock = createSequentialLockDecorator({ store });
class DataService {
@SequentialLock('fetch-data')
async fetchData(): Promise<void> { /* ... */ }
@SequentialLock(args => `price:${args[0]}`)
async updatePrice(sku: string): Promise<void> { /* ... */ }
@SequentialLock({ key: 'payment', timeoutMs: 5000 })
async charge(amount: number): Promise<string> { /* ... */ }
}Key-fn args is inferred from the method signature — no annotations needed. The K generic constrains the decorated method to (...args) => Promise<unknown>; sync methods fail at compile time and, if cast-bypassed, reject at runtime.
Exclusive (Promise)
createExclusiveLockDecorator
No timeoutMs/signal — ExclusiveLockArgumentType only accepts string | ((args) => string) | { key }, so there is nothing to wait on. A compliant store's acquire() is expected to reject immediately (no queueing) with LockBusyError when the key is already held; the decorator itself just propagates that rejection.
import { createExclusiveLockDecorator } from '@rnw-community/lock-decorator';
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
declare const store: LockStoreInterface;
const ExclusiveLock = createExclusiveLockDecorator({ store });
class Cache {
@ExclusiveLock('cache-write')
async write(value: string): Promise<void> { /* ... */ }
}Observable variants — $ factories
For methods that return Observable<T>, use createSequentialLockDecorator$ / createExclusiveLockDecorator$. Same store contract, same key-argument shapes. The acquired handle is released on the inner Observable's complete, error, or unsubscribe — the lock tracks the subscription lifecycle. Unlike the Promise variants above, the $ factories bridge an external AbortSignal themselves: aborting it errors the subscriber with DOMException('The operation was aborted.', 'AbortError') directly, independent of what the store does.
createSequentialLockDecorator$
import { createSequentialLockDecorator$ } from '@rnw-community/lock-decorator';
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
import type { Observable } from 'rxjs';
declare const store: LockStoreInterface;
const SequentialLock$ = createSequentialLockDecorator$({ store });
class StreamService {
@SequentialLock$({ key: 'feed', timeoutMs: 1000 })
subscribe$(symbol: string): Observable<number> { /* ... */ }
}createExclusiveLockDecorator$
import { createExclusiveLockDecorator$ } from '@rnw-community/lock-decorator';
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
import type { Observable } from 'rxjs';
declare const store: LockStoreInterface;
const ExclusiveLock$ = createExclusiveLockDecorator$({ store });
class StreamService {
@ExclusiveLock$({ key: 'feed' })
subscribe$(symbol: string): Observable<number> { /* ... */ }
}Raw middleware
If you are building a custom decorator (for example a DI-aware NestJS adapter), consume the raw middleware directly and feed it into your own createInterceptor({ middleware }) call. Both are used internally by the four factories above.
createLockMiddleware
Returns an InterceptorMiddleware<TArgs> for Promise-returning methods:
import { createInterceptor } from '@rnw-community/decorators-core';
import { createLockMiddleware } from '@rnw-community/lock-decorator';
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
declare const store: LockStoreInterface;
const withSequentialLock = createInterceptor({ middleware: createLockMiddleware(store, 'sequential', 'my-key') });createLockMiddleware$
Returns an InterceptorMiddleware<TArgs, Observable<unknown>> for Observable-returning methods, and additionally bridges an external AbortSignal through to the store:
import { createInterceptor } from '@rnw-community/decorators-core';
import { createLockMiddleware$ } from '@rnw-community/lock-decorator';
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
declare const store: LockStoreInterface;
const withSequentialLock$ = createInterceptor({ middleware: createLockMiddleware$(store, 'sequential', 'my-key') });Store contract
Bring your own LockStoreInterface implementation — Redis, in-process, cluster-aware, whatever fits the deployment target. The store returns a handle; the lock decorators/middleware call the handle's release() for you — when the protected Promise settles for the Promise variants, or when the Observable completes, errors, or unsubscribes for the $ variants. A minimal adapter is typically a few dozen lines.
LockStoreInterface
import type { LockStoreInterface } from '@rnw-community/lock-decorator';
const store: LockStoreInterface = {
acquire: async (key, mode, options) => ({
key,
mode,
release: async () => { /* ... */ },
}),
};LockHandleInterface
The handle returned by LockStoreInterface.acquire; the four factories call release() for you.
import type { LockHandleInterface } from '@rnw-community/lock-decorator';
const handle: LockHandleInterface = { key: 'my-key', mode: 'sequential', release: () => undefined };AcquireOptionsInterface
{ timeoutMs?: number; signal?: AbortSignal } — the third argument to LockStoreInterface.acquire.
import type { AcquireOptionsInterface } from '@rnw-community/lock-decorator';
const options: AcquireOptionsInterface = { timeoutMs: 5000 };LockModeType
'sequential' | 'exclusive' — passed to LockStoreInterface.acquire so the store knows which semantics to apply.
import type { LockModeType } from '@rnw-community/lock-decorator';
const mode: LockModeType = 'sequential';CreateLockOptionsInterface
{ store: LockStoreInterface } — the sole argument to all four factories.
import { createSequentialLockDecorator } from '@rnw-community/lock-decorator';
import type { CreateLockOptionsInterface, LockStoreInterface } from '@rnw-community/lock-decorator';
declare const store: LockStoreInterface;
const options: CreateLockOptionsInterface = { store };
const SequentialLock = createSequentialLockDecorator(options);Errors
Neither of these is thrown by the decorators or createLockMiddleware/createLockMiddleware$ themselves — both are exported as the conventional error classes a LockStoreInterface.acquire() implementation is expected to throw/reject with, so callers get a stable instanceof check no matter which store is plugged in. The library only awaits store.acquire() and propagates whatever it resolves or rejects with.
LockBusyError
Convention: a store's acquire() should reject with this when mode: 'exclusive' and the key is already held.
import { LockBusyError } from '@rnw-community/lock-decorator';
declare const cache: { write: (value: string) => Promise<void> };
try {
await cache.write('value');
} catch (error) {
if (error instanceof LockBusyError) {
console.warn(`busy: ${error.key}`);
}
}LockAcquireTimeoutError
Convention: a store's acquire() should reject with this when mode: 'sequential' and options.timeoutMs elapses before the key becomes free.
import { LockAcquireTimeoutError } from '@rnw-community/lock-decorator';
declare const service: { charge: (amount: number) => Promise<string> };
try {
await service.charge(100);
} catch (error) {
if (error instanceof LockAcquireTimeoutError) {
console.warn(`timed out after ${error.timeoutMs}ms for ${error.key}`);
}
}Key-argument types
SequentialLockArgumentType<TArgs>
Accepted key shapes for createSequentialLockDecorator / createSequentialLockDecorator$:
import type { SequentialLockArgumentType } from '@rnw-community/lock-decorator';
const byId: SequentialLockArgumentType<[id: string]> = ([id]) => `order:${id}`;ExclusiveLockArgumentType<TArgs>
Accepted key shapes for createExclusiveLockDecorator / createExclusiveLockDecorator$ — no timeoutMs/signal, exclusive locks never wait:
import type { ExclusiveLockArgumentType } from '@rnw-community/lock-decorator';
const byId: ExclusiveLockArgumentType<[id: string]> = ([id]) => ({ key: `cache:${id}` });LockArgumentType<TArgs>
SequentialLockArgumentType<TArgs> | ExclusiveLockArgumentType<TArgs> — the union accepted internally by createLockMiddleware / createLockMiddleware$.
import type { LockArgumentType } from '@rnw-community/lock-decorator';
const arg: LockArgumentType<[id: string]> = 'static-key';