Packages
All PraxisJS packages, their stability, current versions, and install commands.
Packages
All public packages published to npm. Versions follow semantic versioning — breaking changes only happen in major bumps.
PraxisJS itself is stable and production-ready: no surprise API changes (breaking changes require a major version bump), deprecations before removal, and test coverage across every package. Docs are updated alongside releases, not after. A handful of newer packages are still settling — those are marked Beta or Experimental below.
Foundation
Core packages that every PraxisJS project depends on. All stable.
| Package | Version | Description |
|---|---|---|
@praxisjs/core | 2.3.1 | Reactivity engine — signal, computed, effect, batch, peek, untrack, selector, resource |
@praxisjs/decorators | 2.0.1 | Class component decorators — @State, @Prop, @FunctionProp, @Watch, @Emit, @Compose, @Resource, @Ref, @Command, @Selector |
@praxisjs/runtime | 0.8.2 | DOM renderer — mounts components, manages scopes, handles reactive children, keyed lists (For, Index), Portal, SSG hydration |
@praxisjs/jsx | 0.8.2 | JSX runtime (jsx-runtime, jsx-dev-runtime) |
@praxisjs/shared | 0.3.2 | Shared types and internal utilities (not installed directly) |
npm install @praxisjs/core @praxisjs/decorators @praxisjs/runtime @praxisjs/jsxpnpm add @praxisjs/core @praxisjs/decorators @praxisjs/runtime @praxisjs/jsxyarn add @praxisjs/core @praxisjs/decorators @praxisjs/runtime @praxisjs/jsxbun add @praxisjs/core @praxisjs/decorators @praxisjs/runtime @praxisjs/jsxPackages
First-party plugins — install only what your project needs. All stable.
| Package | Version | Description |
|---|---|---|
@praxisjs/head | 0.3.3 | Reactive document head — @Head decorator for title, meta, og:, twitter: |
@praxisjs/content | 0.2.3 | Markdown content collections with @Collection, @PagedCollection, frontmatter validation, and Vite plugin |
@praxisjs/router | 2.3.2 | Client-side router with @Router, @Route, named routes, route meta, and scroll restoration |
@praxisjs/store | 2.0.6 | Class-based singleton state with @Storable, @Store, and plugin system |
@praxisjs/di | 1.3.15 | Decorator-based dependency injection with scoped containers |
@praxisjs/motion | 1.2.1 | @Tween and @Spring animated field decorators, createTransition |
@praxisjs/fsm | 2.2.2 | @StateMachine and @Transition finite state machines |
@praxisjs/concurrent | 1.3.10 | @Task, @Queue, @Pool async concurrency control with opt-in AbortSignal |
Head
npm install @praxisjs/headpnpm add @praxisjs/headyarn add @praxisjs/headbun add @praxisjs/headContent
npm install @praxisjs/contentpnpm add @praxisjs/contentyarn add @praxisjs/contentbun add @praxisjs/contentRouter
npm install @praxisjs/routerpnpm add @praxisjs/routeryarn add @praxisjs/routerbun add @praxisjs/routerStore
npm install @praxisjs/storepnpm add @praxisjs/storeyarn add @praxisjs/storebun add @praxisjs/storeDI
npm install @praxisjs/dipnpm add @praxisjs/diyarn add @praxisjs/dibun add @praxisjs/diMotion
npm install @praxisjs/motionpnpm add @praxisjs/motionyarn add @praxisjs/motionbun add @praxisjs/motionFSM
npm install @praxisjs/fsmpnpm add @praxisjs/fsmyarn add @praxisjs/fsmbun add @praxisjs/fsmConcurrency
npm install @praxisjs/concurrentpnpm add @praxisjs/concurrentyarn add @praxisjs/concurrentbun add @praxisjs/concurrentUtilities
All stable.
| Package | Version | Description |
|---|---|---|
@praxisjs/composables | 1.2.3 | DOM, browser, list, and file upload composable classes via @Compose |
@praxisjs/css | 0.3.6 | Scoped CSS with typed class names (@Styled), reactive CSS properties (@Style), design tokens, and static build-time extraction via the Vite plugin |
npm install @praxisjs/composablespnpm add @praxisjs/composablesyarn add @praxisjs/composablesbun add @praxisjs/composablesCSS
npm install @praxisjs/csspnpm add @praxisjs/cssyarn add @praxisjs/cssbun add @praxisjs/cssTooling
| Package | Version | Status | Description |
|---|---|---|---|
@praxisjs/vite-plugin | 4.2.2 | Stable | Vite integration — decorators, JSX transform, compiled templates, keyed list rewrite, HMR, library compilation, and CSS static extraction |
@praxisjs/ssg | 0.1.5 | Experimental | Static site generation — prerenders routes to HTML and hydrates them client-side |
@praxisjs/devtools | 0.3.2 | Beta | In-app signal inspector and component profiler |
@praxisjs/storybook | 0.3.3 | Stable | Storybook framework adapter |
@praxisjs/mcp | 0.4.0 | Beta | MCP server — docs, API reference, project inspection, validation and project memory for AI assistants |
Vite Plugin
npm install -D @praxisjs/vite-pluginpnpm add -D @praxisjs/vite-pluginyarn add -D @praxisjs/vite-pluginbun add -d @praxisjs/vite-pluginSSG
npm install -D @praxisjs/ssgpnpm add -D @praxisjs/ssgyarn add -D @praxisjs/ssgbun add -d @praxisjs/ssgDevTools
npm install -D @praxisjs/devtoolspnpm add -D @praxisjs/devtoolsyarn add -D @praxisjs/devtoolsbun add -d @praxisjs/devtoolsStorybook
npm install -D @praxisjs/storybookpnpm add -D @praxisjs/storybookyarn add -D @praxisjs/storybookbun add -d @praxisjs/storybookMCP
npm install -D @praxisjs/mcppnpm add -D @praxisjs/mcpyarn add -D @praxisjs/mcpbun add -d @praxisjs/mcpCLI
Both stable.
| Package | Version | Description |
|---|---|---|
create-praxisjs | 1.2.1 | Project scaffolding CLI |
praxisjs | 1.2.4 | Maintenance CLI for existing projects — add kosmesis, ai add/ai remove/ai sync, doctor, upgrade |
Scaffold a new project
npm create praxisjs@latestMaintain an existing project
npx praxisjs ai add
npx praxisjs ai remove
npx praxisjs doctor
npx praxisjs upgradeSee the praxisjs CLI reference for what each command checks, installs, or updates.
Why it was built
PraxisJS started as a personal exploration of what a more explicit, traceable frontend architecture could look like — one where reactivity is a first-class, visible contract rather than an implementation detail.
It also became an experiment in AI-assisted development: not to automate thinking, but to pressure-test ideas, surface blind spots, and accelerate iteration on the design.
Contributing
Found a bug? Have an idea? Contributions are welcome at any level.
- Open an issue — bug reports, feature requests, or questions
- Submit a pull request — fixes, improvements, new features