SDuX Vault — a zero-dependency, pipeline-based state engine for Deno (no install, just npm:@sdux-vault/core)

[SDuXVault]

I got tired of boilerplate, ceremony, race conditions and middleware spaghetti, so I built something different.

SDuX Vault is a pipeline-based state management engine. Pure TypeScript, zero dependencies. Every state change flows through a deterministic pipeline (resolve, merge, filter, reduce, persist, etc.) in guaranteed order. That gives you atomic updates, no race conditions, built-in tab sync, encryption, and circuit breaker controllers.

Watch: 5-minute overview

It runs anywhere TypeScript runs. On Deno there's nothing to install — you import it directly through an npm: specifier:

import { FeatureCell, Vault } from 'npm:@sdux-vault/core';

// Initialize the Vault runtime once, before any cell is created
Vault({ logLevel: 'off', devMode: false });

const cell = FeatureCell<CounterState>({
  key: 'counter',
  initialState: { count: 0, label: 'Counter Example' }
});

cell.initialize();

cell.replaceState({ count: 1, label: 'Counter is 1' });

Because a FeatureCell is headless plain TypeScript with no framework dependency, it's a natural fit for Deno CLIs, scripts, background jobs, and edge functions — deterministic state handling without pulling in a UI framework. Same universal @sdux-vault/core API across every runtime. No adapters, no wrappers.

What it gives you

• Deterministic pipeline — stages execute in guaranteed order every time
• Atomic state commitment — no partial or torn updates
• Built-in tab sync, encryption, and circuit breaker controllers
• Zero dependencies — pure TypeScript, imported straight from npm:@sdux-vault/core
• One universal API — the same @sdux-vault/core everywhere

Links

• Blog (Deno walkthrough): https://www.sdux-vault.com/blog/state-management-without-a-ui-on-deno
• Deno examples: https://www.sdux-vault.com/stackblitz#deno
• Docs: https://www.sdux-vault.com/docs
• GitHub: https://github.com/sdux-vault
• Chrome DevTools: https://chromewebstore.google.com/detail/sdux-vault-devtools/ahhijigegohpaegehjhdojcldgigbekh
• NPM: https://www.npmjs.com/package/@sdux-vault/core

If you're curious, try it in a Deno side project and let me know what you think. I'd love honest feedback — what works, what's confusing, what feels wrong. Reply in this thread or open an issue on GitHub.

I'm a solo developer on this — it's not a funded project. Just a senior engineer who built the tool I wished existed. Reply in this thread or reach out at sduxvault@gmail.com.

One question to kick things off: does importing state management straight from npm:@sdux-vault/core feel natural in Deno, or would you expect a Deno-specific module or jsr: package? Curious where your instincts land.