npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@reactive-contracts/compiler

v0.2.0

Published

Build-time compiler and validator for Reactive Contracts

Readme

@reactive-contracts/compiler

Build-time compiler and CLI for Reactive Contracts - generates type-safe code from your contract definitions.

Installation

npm install @reactive-contracts/compiler
# or
yarn add @reactive-contracts/compiler
# or
pnpm add @reactive-contracts/compiler

CLI Usage

The compiler provides a CLI tool called rcontracts:

Initialize a Project

npx rcontracts init

This creates:

  • rcontracts.config.ts - Configuration file
  • contracts/ - Directory for your contract definitions
  • contracts/sample.contract.ts - Example contract

Compile Contracts

npx rcontracts compile

Compiles all contracts and generates:

  • Frontend code - Type-safe hooks and client utilities
  • Backend code - Resolver stubs and type definitions
  • Runtime utilities - Shared validation and types

Validate Contracts

npx rcontracts validate

Validates all contracts without generating code. Useful for CI pipelines.

Diagnose a Contract

npx rcontracts diagnose UserProfile

Shows detailed analysis for a specific contract including:

  • Shape analysis
  • Constraint validation
  • Reactivity configuration
  • Potential issues

Show Changes

npx rcontracts diff

Shows changes since last compile.

Run Migrations

npx rcontracts migrate

Runs contract migrations for version updates.

Configuration

Create a rcontracts.config.ts in your project root:

import { defineConfig } from '@reactive-contracts/compiler';

export default defineConfig({
  // Directory containing your .contract.ts files
  contractsDir: './contracts',
  
  // Output directory for generated code
  outputDir: './generated',
  
  // Generate frontend code (React hooks, etc.)
  generateFrontend: true,
  
  // Generate backend code (resolvers, etc.)
  generateBackend: true,
  
  // Enable strict validation
  strict: true,
});

Programmatic API

You can also use the compiler programmatically:

import { compile, validate } from '@reactive-contracts/compiler';

// Compile contracts
await compile({
  contractsDir: './contracts',
  outputDir: './generated',
});

// Validate only
const result = await validate({
  contractsDir: './contracts',
});

if (!result.valid) {
  console.error('Validation errors:', result.errors);
}

Generated Code Structure

After running rcontracts compile, the output directory will contain:

generated/
├── frontend/
│   ├── UserProfile.ts      # React hooks and client code
│   └── ...
├── backend/
│   ├── UserProfile.resolver.ts  # Resolver stubs
│   └── ...
└── runtime/
    ├── types.ts            # Shared types
    └── validation.ts       # Runtime validation

Integration with Build Tools

Vite

// vite.config.ts
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    // Run rcontracts compile before build
    {
      name: 'reactive-contracts',
      buildStart: async () => {
        const { compile } = await import('@reactive-contracts/compiler');
        await compile();
      },
    },
  ],
});

package.json scripts

{
  "scripts": {
    "contracts:compile": "rcontracts compile",
    "contracts:validate": "rcontracts validate",
    "contracts:watch": "rcontracts compile --watch",
    "prebuild": "pnpm contracts:compile"
  }
}

Related Packages

License

MIT