[ OPEN SOURCE · @VLLNT ON NPM ]
The code we build on, released.
The libraries, Convex components and UI behind vllnt, published on npm under @vllnt. Read them, reuse them, fork them.
pnpm add @vllnt/loggerpnpm add @vllnt/convex-flagspnpm add @vllnt/ui- Packages33
- Convex components23
- LicenceMIT
- Registrynpm
[ § 01 · CONVEX COMPONENTS ]
Backend building blocks for Convex.
23 components you add to a Convex app one at a time. Each keeps its data in its own tables, so adding one never touches your schema.
STABLE 0.1.0 · 3 GitHub stars
@vllnt/convex-flags
Feature flags — variants, targeting, percentage rollouts, and per-subject overrides, evaluated on the backend and streamed live to clients
STABLE 0.1.0 · 1 GitHub star
@vllnt/convex-consent
Append-only consent ledger (GDPR Art. 6/7) — record, withdraw, and gate consent per subject + purpose
STABLE 0.1.0 · 2 GitHub stars
@vllnt/convex-notifications
Per-subject directed inbox — deliver notifications with read/unread state and fan-out
STABLE 0.2.0 · 1 GitHub star
@vllnt/convex-api-keys
Convex component for secure API key management — create, validate, revoke, rotate, and track usage
STABLE 0.1.0 · 2 GitHub stars
@vllnt/convex-analytics
Generic, configurable analytics component for Convex — any event, any dimension, any domain; rollup-on-write with funnels, retention, uniques
[ § 02 · UI ]
One design system, web and native.
The components behind every vllnt site, for React on the web and React Native on phones.
STABLE 0.3.0 · 9 GitHub stars
@vllnt/ui
React component library built on Radix UI, Tailwind CSS and CVA
CANARY ONLY · 9 GitHub stars
@vllnt/ui-core
Platform-neutral design tokens and component contracts for VLLNT UI renderers
[ § 03 · LIBRARIES AND TOOLING ]
The rest of the toolbox.
Logging, analytics, lint and TypeScript configs, and helpers for Convex and Next.js.
Lightweight, privacy-first analytics with consent management and React integration
STABLE 0.1.1 · 1 GitHub star
Typed host-side helpers for Convex backends — builders, errors, validators, relationships, pagination, HTTP, env, and observability
STABLE 0.1.0 · 1 GitHub star
TypeScript client for a local dig daemon — search, organize, reconcile, and export a knowledge base over HTTP
CANARY ONLY · 4 GitHub stars
Strict ESLint config for TypeScript projects. All rules enforce error — no warnings
STABLE 2.1.0 · 2 GitHub stars
Structured logging for the @vllnt ecosystem
STABLE 0.1.2 · 2 GitHub stars
AI discoverability for Next.js sites — generate llms.txt / llms-full.txt manifests and serve any page as raw markdown
CANARY ONLY · 1 GitHub star
Shared TypeScript configurations for vllnt projects
STABLE 3.0.0 · 1 GitHub star
[ § 04 · HOW WE PUBLISH ]
Canary first, then stable.
Every package ships the same way, so you know what you install.
Canary
Every change merged to main publishes a prerelease build. Its API may still change.
Stable
A tagged release publishes a regular version on npm, the default install.
Rollback
A broken version is deprecated on npm, never unpublished, so your lockfile keeps working.
[ § 05 · WHAT WE COMMIT TO ]
Open where it counts.
Written down, so you can hold us to them.
- Licences
- MIT, with one Apache-2.0 package
- Source
- Each package links to its public source repository
- Issues
- Opened on the package’s source repository
- Registry
- npm, under the @vllnt scope
Build without depending on anyone.
Install a package, read its source, or open an issue on its repository.