Plugin Catalog

This catalog lists all published plugins and packages in the Setu-TS framework, organized by tier and capability.

Package Tiers

Packages are organized into tiers based on their role in the framework:

Optional npm drivers

Most packages depend on nothing but their @setu-ts/* siblings. Where a package offers a driver — a Redis client, a cloud SDK, a database ORM — it declares that driver as an optional peer dependency, and the rule is always the same: nothing is imported until you select the arm that needs it. Choosing MemoryStore never loads ioredis; choosing LogProvider never loads nodemailer.

Three packages are the exception, and the table marks them always: for graphql-plugin, grpc-plugin and react-router-plugin the driver is the capability rather than one choice among several, so there is nothing to select. Their driver is still an optional peer, so it is still yours to install.

A package manager never installs an optional peer. Installing @setu-ts/messaging-plugin brings none of its six broker clients; selecting the Kafka arm without kafkajs installed fails at startup with OptionalDependencyUnavailableError naming the package and its installation location. Install the driver for the arm you select, beside the plugin:

npm install @setu-ts/messaging-plugin kafkajs
# Deno: deno add npm:@setu-ts/messaging-plugin npm:kafkajs

setu new --broker/--queue and a workspace’s --transport already add the client for the arm they wire. setu add records peers for the default arm it wires (for example the console telemetry exporter); any other arm you select by hand needs its driver installed as above.

Optional peers in a workspace

Install an optional peer where the framework package that loads it is installed, within the version range that package declares for it (in its peerDependencies, or dependencies for the few loaders that declare their package as a regular dependency). In an npm, Yarn or Bun workspace this is usually the workspace root. A hoisted framework package resolves imports from its own location: a peer nested under a member is invisible to it. Conflicting member pins can also produce two copies of a peer, including incompatible versions.

The startup symptom is Optional dependency '<d>' could not be loaded by '<package>', followed by the instruction to install it where that package is installed. Check the installed framework package’s package.json for its peer ranges rather than installing the latest upstream major.

Since 0.11.0, setu add <plugin> --dir apps/<member> in a listed Node or Bun Setu workspace records the peers it supplies in the member’s package.json dependencies and, when the root has a package.json, in the root’s too. It leaves a peer already declared in dependencies, optionalDependencies or a non-optional peerDependencies as it is, adds a peer marked optional in peerDependenciesMeta to dependencies at its own spec (it installs nothing otherwise), moves one declared only in devDependencies to dependencies with its pin unchanged (--omit=dev would drop it), records a peer the root’s overrides pins (a string value, or an object’s "." entry) at the override’s own spec (npm refuses a direct dependency whose spec differs from its override), leaves a $name reference or a conditional override (a version-selector key such as ioredis@5, or several rules for one package) to you with a printed line, still writes the root entry at the CLI’s range when a workspace member pins the peer at a different spec, printing a note that names the member and its pin since npm may install a second copy for it, refuses a root package.json that is JSONC or invalid JSON by name, and prints every edited path; run the printed install command from the workspace root. The member entry also supports building the member outside the workspace. Deno workspaces, standalone projects, pnpm workspaces and hand-built Yarn workspaces keep their existing behavior; place peers manually when needed. setu add still refuses a workspace root as its target.

Three packages carry a real (non-optional) dependency beyond their siblings: kernel depends on hono (its router), runtime on @hono/node-server (the Node adapter), and view-plugin on hono (both view engines).

Which packages declare drivers

Every package NOT listed here declares no optional driver — that includes common, kernel, exceptions, sdk, cloudflare-plugin, session-plugin, validation-plugin, openapi-plugin, static-plugin, websocket-plugin, worker-pool-plugin, diagnostics-plugin, view-plugin, and the three starters. cli is on that list too, which is worth saying out loud because its source is full of package names: those are DATA it writes into a generated project’s manifest, not specifiers it imports.

The three always rows — graphql-plugin, grpc-plugin and react-router-plugin — have no zero-driver arm, and none of them claims one. Everything else here is genuinely optional: the arm named beside it is the only thing that loads it.

Every driver above can also be supplied by injection instead, through the plugin’s own options (DatabasePlugin({ client }), CachePlugin({ client }), and so on). An application that injects its own client never triggers the lazy import at all — see AI_GUIDELINES §12.2.

node-redis. Every ioredis row above can run on node-redis (redis v5 or v6) through that injection: wrap a client in fromNodeRedis from @setu-ts/common and pass it as the plugin’s client (the backplane takes client and subscriber). ioredis is then never loaded, and redis is your application’s own dependency, which no Setu-TS package declares. Traces come from instrumentations.redis in telemetry-plugin, on Node only. See Using node-redis and setu new --redis-client node-redis in the CLI guide.

Tier 1: Core Infrastructure

@setu-ts/common

Purpose: Shared types, interfaces, and capability tokens used across all packages.

Capability Token: N/A (contracts and shared pure utilities)

Runtime Compatibility:

Key Exports:

• IPlugin, IPluginContext - Plugin contracts
• CAPABILITIES - Standard capability tokens
• IRequest, IResponse, IRequestContext - HTTP abstractions
• IRuntimeServices - Runtime service interface

Links:

• README
• API Reference

@setu-ts/kernel

Purpose: Core plugin kernel with registry, middleware pipeline, router, and application lifecycle.

Capability Token: N/A (core infrastructure)

Runtime Compatibility:

Key Exports:

• createApplication() - Application factory; its only value export. The router, service registry and pipeline are reached through the application (app.router, app.services, app.middleware), not imported

Links:

• README
• API Reference

@setu-ts/runtime

Purpose: Runtime detection and HTTP adapter implementations for all platforms.

Capability Token: CAPABILITIES.RUNTIME

Runtime Compatibility:

Key Exports:

• RuntimePlugin - Runtime registration
• DenoHttpAdapter, NodeHttpAdapter, BunHttpAdapter, CloudflareWorkersHttpAdapter
• detectRuntime() - Runtime detection

Links:

• README
• API Reference

Tier 2: Essential Plugins

@setu-ts/di-plugin

Purpose: Optional dependency injection container with constructor injection and scope management.

Capability Token: CAPABILITIES.DI_CONTAINER

Runtime Compatibility:

Key Features:

• Singleton, scoped, and transient lifecycles
• Constructor and parameter injection
• Circular dependency detection
• Hierarchical scopes

Links:

• README
• API Reference

@setu-ts/decorator-plugin

Purpose: Optional decorators for controllers, routes, and dependency injection.

Capability Token: CAPABILITIES.METADATA_STORE

Runtime Compatibility:

Key Features:

• @Controller, @Get, @Post, etc.
• @Injectable, @Inject
• @Body, @Query, @Param
• @UseGuards, @UseInterceptors, @UseFilters

Note: Decorators are optional and require explicit token injection (no emitDecoratorMetadata).

Links:

• README
• API Reference

@setu-ts/logger-plugin

Purpose: Structured logging with pluggable backends.

Capability Token: CAPABILITIES.LOGGER

Runtime Compatibility:

Key Features:

• Console and file backends
• Log levels (debug, info, warn, error)
• Structured JSON output
• Context injection

Links:

• README
• API Reference

@setu-ts/config-plugin

Purpose: Configuration management with environment variable support and validation.

Capability Token: CAPABILITIES.CONFIG

Runtime Compatibility:

Key Features:

• Environment variable loading
• Variable expansion (${VAR})
• Zod-compatible validation
• Multi-source configuration

Links:

• README
• API Reference

@setu-ts/validation-plugin

Purpose: Request validation with Zod integration.

Capability Token: CAPABILITIES.VALIDATION

Runtime Compatibility:

Key Features:

• Zod schema validation
• Request body/query/param validation
• Custom error formatting
• Async validators

Links:

• README
• API Reference

@setu-ts/exceptions

Purpose: Exception hierarchy, RFC 9457 Problem Details, and the error-handler middleware.

Capability Token: N/A (middleware-only)

Runtime Compatibility:

Features:

• HttpError hierarchy
• RFC 9457 Problem Details format (the 'rfc7807' alias is deprecated but still accepted)
• Error handler middleware factory

Links:

• README
• API Reference

@setu-ts/openapi-plugin

Purpose: OpenAPI 3.1 spec generation from routes, with a Zod transformer and Swagger UI.

Capability Token: CAPABILITIES.OPENAPI

Runtime Compatibility:

Features:

• Route-based OpenAPI spec generation
• Zod schema transformer
• Swagger UI serving

Links:

• README
• API Reference

Tier 3: Business Capabilities

@setu-ts/database-plugin

Purpose: Database access with repository pattern and ORM adapters.

Capability Token: CAPABILITIES.DATABASE

Runtime Compatibility:

Adapters:

• Memory (built-in)
• Prisma (an injected Prisma v7 client)
• Drizzle (an injected Drizzle database, wrapped with createDrizzleDatabase)
• MongoDB (via mongodb)
• DynamoDB (via @aws-sdk/client-dynamodb)
• Azure Cosmos DB (via @azure/cosmos)
• Cloud Bigtable (via @google-cloud/bigtable)
• Custom (type: 'custom'), for example D1Adapter from cloudflare-plugin

Links:

• README
• API Reference

@setu-ts/cache-plugin

Purpose: Caching with multiple backend support.

Capability Token: CAPABILITIES.CACHE

Runtime Compatibility:

Stores:

• Memory (built-in)
• Redis (via ioredis)
• Cloudflare KV

Links:

• README
• API Reference

@setu-ts/auth-plugin

Purpose: Authentication and authorization with JWT and API key support.

Capability Token: CAPABILITIES.AUTH, CAPABILITIES.AUTHORIZATION

Runtime Compatibility:

Features:

• JWT (HS256, RS256)
• API key authentication
• RBAC with role hierarchy
• Local strategy for login flows
• Password hashing (PBKDF2-SHA256)
• Tokens from an outside issuer, verified against its published key set (issuers)
• Sign-in with an outside provider: OpenID Connect, OAuth 2.0 and SAML 2.0 (signIn)
• Multi-factor authentication: TOTP with recovery codes, and passkeys (WebAuthn)

Links:

• README
• API Reference

@setu-ts/messaging-plugin

Purpose: Message broker integration for event-driven architectures.

Capability Token: CAPABILITIES.MESSAGING

Runtime Compatibility:

Brokers:

• In-memory (built-in)
• Redis Streams (via ioredis)
• RabbitMQ (via amqplib)
• NATS (via nats)
• Kafka (via kafkajs)
• GCP Pub/Sub (via @google-cloud/pubsub)
• Azure Service Bus (via @azure/service-bus)

Workers is not supported by this package: every broker except the in-memory default needs raw sockets or an npm SDK that does not run on the edge. The capability itself IS available there — @setu-ts/cloudflare-plugin registers CAPABILITIES.MESSAGING from the platform, serving publish/subscribe over Workers Queues and request/reply through a Durable Object reply inbox. An application registers exactly one provider of the token, so the choice is per deployment target, not per call site.

Features:

• Publish/subscribe
• Request/reply (RPC)
• Events bridge
• Durable delivery where the broker provides it

Links:

• README
• API Reference

@setu-ts/queue-plugin

Purpose: Job queue with retries, scheduling, and multiple backends.

Capability Token: CAPABILITIES.QUEUE

Runtime Compatibility:

Adapters:

• Memory (built-in)
• Redis (via ioredis)
• RabbitMQ (via amqplib)
• SQS (via @aws-sdk/client-sqs)

Workers Queues belong to @setu-ts/cloudflare-plugin, not this package — the queue-plugin adapters all need raw sockets or an npm SDK unavailable on the edge.

Links:

• README
• API Reference

@setu-ts/events-plugin

Purpose: Domain event publishing and handling.

Capability Token: CAPABILITIES.EVENTS

Runtime Compatibility:

Features:

• DomainEvent, IntegrationEvent
• In-memory event bus
• Aggregate-local recording (createDomainEvents)
• Forwarding to a broker through messaging-plugin’s EventsMessagingBridge

Links:

• README
• API Reference

@setu-ts/cqrs-plugin

Purpose: Command-Query Responsibility Segregation pattern implementation.

Capability Token: CAPABILITIES.CQRS

Runtime Compatibility:

Features:

• CommandBus, QueryBus
• Handler registration
• Pipeline behaviors

Links:

• README
• API Reference

Tier 4: Infrastructure

@setu-ts/metrics-plugin

Purpose: Prometheus metrics collection.

Capability Token: CAPABILITIES.METRICS

Runtime Compatibility:

Features:

• Counter, Gauge, Histogram, Summary
• HTTP metrics collection
• /metrics endpoint

Links:

• README
• API Reference

@setu-ts/health-plugin

Purpose: Health checks and readiness probes.

Capability Token: CAPABILITIES.HEALTH

Runtime Compatibility:

Features:

• Built-in health indicators
• Custom health checks
• Aggregated health endpoint

Links:

• README
• API Reference

@setu-ts/telemetry-plugin

Purpose: OpenTelemetry integration for distributed tracing.

Capability Token: CAPABILITIES.TELEMETRY

Runtime Compatibility:

Features:

• Request tracing
• W3C traceparent propagation
• OTLP exporter
• Auto-instrumentation (Node-only)

Links:

• README
• API Reference

@setu-ts/scheduler-plugin

Purpose: Scheduled job execution with cron support.

Capability Token: CAPABILITIES.SCHEDULER

Runtime Compatibility:

Features:

• 5-field UTC cron parser
• Fixed-interval and one-shot jobs
• Retry with backoff
• Distributed locking

Links:

• README
• API Reference

@setu-ts/secrets-plugin

Purpose: Secret management with multiple cloud providers.

Capability Token: CAPABILITIES.SECRETS

Runtime Compatibility:

Providers:

• Environment variables (default)
• AWS Secrets Manager
• GCP Secret Manager
• Azure Key Vault
• HashiCorp Vault

Links:

• README
• API Reference

@setu-ts/audit-plugin

Purpose: Audit logging with pluggable storage.

Capability Token: CAPABILITIES.AUDIT

Runtime Compatibility:

Storage:

• Memory (default)
• File (JSONL)
• Database (an injected client)
• Log (routes each entry to the logger; query() returns [])

Links:

• README
• API Reference

@setu-ts/resilience-plugin

Purpose: Resilience patterns (circuit breaker, retry, timeout, bulkhead).

Capability Token: CAPABILITIES.RESILIENCE

Runtime Compatibility:

Patterns:

• Circuit breaker
• Retry with backoff
• Timeout
• Bulkhead

Links:

• README
• API Reference

@setu-ts/storage-plugin

Purpose: Object storage with multiple cloud providers.

Capability Token: CAPABILITIES.STORAGE

Runtime Compatibility:

Providers:

• Memory (default)
• Local filesystem
• AWS S3
• Google Cloud Storage
• Azure Blob Storage
• Backblaze B2

Links:

• README
• API Reference

@setu-ts/mail-plugin

Purpose: Email sending with multiple providers.

Capability Token: CAPABILITIES.MAIL

Runtime Compatibility:

Providers:

• Log (default, for development)
• SMTP (Node/Deno/Bun only)
• AWS SES
• SendGrid

Links:

• README
• API Reference

@setu-ts/notification-plugin

Purpose: Multi-channel notifications (email, SMS, push, Slack).

Capability Token: CAPABILITIES.NOTIFICATION

Runtime Compatibility:

Channels:

• Email (via mail plugin)
• SMS (Twilio)
• Push (FCM)
• Slack

Links:

• README
• API Reference

@setu-ts/feature-flags-plugin

Purpose: Feature flag management with multiple providers.

Capability Token: CAPABILITIES.FEATURE_FLAGS

Runtime Compatibility:

Providers:

• Config (inline, immutable)
• Memory (mutable)
• Database (polling)
• LaunchDarkly (lazy-loads the Node server SDK)

Links:

• README
• API Reference

@setu-ts/multi-tenancy-plugin

Purpose: Multi-tenancy with multiple isolation strategies.

Capability Token: CAPABILITIES.MULTI_TENANCY

Runtime Compatibility:

Strategies:

• Column isolation (the shipped memory store)
• Schema and database isolation (names a strategy an injected dataStore implements; the memory store refuses both at startup)

Resolvers:

• Subdomain
• Header
• Path
• JWT

Links:

• README
• API Reference

@setu-ts/session-plugin

Purpose: Cookie-based sessions and CSRF protection.

Capability Token: CAPABILITIES.SESSION

Runtime Compatibility:

Features:

• Encrypted cookies (default)
• Server-side storage (memory, cache)
• Key rotation
• Form CSRF (synchronizer token)

Links:

• README
• API Reference

@setu-ts/idempotency-plugin

Purpose: A repeat of a completed HTTP request, queue job or broker message is answered from its record or skipped instead of running again, over one claim/complete/release state machine and an in-process, Redis or Cloudflare Durable Object store. A failure after an external side effect but before complete can still repeat that effect; see the package README for the limits.

Capability Token: CAPABILITIES.IDEMPOTENCY

Runtime Compatibility:

Features:

• idempotent() middleware for a route’s middleware array and idempotentIngress() for queue and broker behaviours on an explicit allow-list
• An in-process store, a Redis store (atomic Lua, inject-or-lazy ioredis) and, from @setu-ts/cloudflare-plugin, a Durable Object store
• The idempotency health indicator: lifecycle truth then a bounded store probe

On Cloudflare Workers, HTTP is supported through the Durable Object store; the ingress entry point is not available there in this release. The guarantee is no duplicate processing within the limits of the store, not a single-execution guarantee.

Links:

• README
• API Reference

@setu-ts/localization-plugin

Purpose: Message catalogues per locale, request locale resolution, and a formatter shared with the browser.

Capability Token: CAPABILITIES.LOCALIZATION

Runtime Compatibility:

Features:

• Catalogues validated at startup; plural forms through Intl.PluralRules
• Locale resolved from query, cookie, Accept-Language or a tenant default into ctx.request.locale
• Vary and Content-Language headers; cache-plugin keys on the locale
• An import-free /format subpath for browsers and SDK clients

Locale data comes from each runtime’s Intl, so a thin ICU build can lack a locale — the plugin refuses such a tag at startup rather than silently formatting in the runtime’s default.

Links:

• README
• API Reference

Tier 5: Platform-Specific

@setu-ts/cloudflare-plugin

Purpose: Cloudflare Workers platform integration.

Capability Token: CAPABILITIES.CLOUDFLARE

Runtime Compatibility:

Features:

• KV cache/session stores
• D1 database adapter
• R2 storage provider
• Durable Objects (backplane, locks)
• Workers Queues
• Cron Triggers
• Messaging (CAPABILITIES.MESSAGING) — publish/subscribe over Workers Queues, and request/reply through a Durable Object reply inbox
• Cache API middleware

Links:

• README
• API Reference

@setu-ts/grpc-plugin

Purpose: gRPC and Connect-ES support.

Capability Token: CAPABILITIES.GRPC

Runtime Compatibility:

Protocols:

• gRPC
• Connect-ES
• gRPC-Web

Links:

• README
• API Reference

@setu-ts/graphql-plugin

Purpose: GraphQL server with schema-first and code-first support.

Capability Token: CAPABILITIES.GRAPHQL

Runtime Compatibility:

Features:

• Schema-first and code-first
• Subscriptions (WebSocket, SSE)
• GraphiQL
• Automatic Persisted Queries

Links:

• README
• API Reference

@setu-ts/react-router-plugin

Purpose: React Router SSR integration.

Capability Token: CAPABILITIES.SSR

Runtime Compatibility:

Note: Requires Node/npm toolchain for client build.

Links:

• README
• API Reference

@setu-ts/sse-plugin

Purpose: Server-Sent Events support.

Capability Token: CAPABILITIES.SSE

Runtime Compatibility:

Links:

• README
• API Reference

@setu-ts/view-plugin

Purpose: Server-rendered HTML as a capability — view engines for JSX and html-tag components, named by reference.

Capability Token: CAPABILITIES.VIEW

Runtime Compatibility:

Views are pure functions rendered to strings — no filesystem, no sockets — so the capability is portable by construction. A tree holding a pending <Suspense> boundary is refused by name (UnresolvedSuspenseError) rather than served as its fallback forever; streaming resolution is deferred to a follow-up milestone.

Links:

• README
• API Reference

@setu-ts/websocket-plugin

Purpose: WebSocket support with room broadcasting.

Capability Token: CAPABILITIES.WEBSOCKET

Runtime Compatibility:

Links:

• README
• API Reference

@setu-ts/diagnostics-plugin

Purpose: Authenticated local diagnostics connector — signed loopback polling between a native devtool client and kernel diagnostics (M98a).

Capability Token: CAPABILITIES.LOCAL_DIAGNOSTICS_LISTENER (consumed; provided by the RuntimePlugin)

Runtime Compatibility:

Links:

• README
• API Reference

@setu-ts/worker-pool-plugin

Purpose: CPU-intensive tasks on worker threads.

Capability Token: CAPABILITIES.WORKER_POOL

Runtime Compatibility:

Links:

• README
• API Reference

@setu-ts/realtime-backplane-plugin

Purpose: Cross-replica real-time communication.

Capability Token: CAPABILITIES.REALTIME_BACKPLANE

Runtime Compatibility:

Transports:

• Memory (default)
• Messaging (brokered)
• Redis
• Custom

The Durable Objects backplane belongs to @setu-ts/cloudflare-plugin, not this package. This plugin ships the memory, messaging, redis, and custom transports; on Workers, register the cloudflare-plugin’s durableObject arm for the DO-backed IRealtimeBackplane instead.

Links:

• README
• API Reference

@setu-ts/static-plugin

Purpose: Static file serving with caching and range requests.

Capability Token: CAPABILITIES.STATIC_FILES

Runtime Compatibility:

Workers has no filesystem, so the plugin registers its capability but mounts no route — a degraded health indicator reports “no file system on this runtime”. Serve assets through Workers Assets or an R2 bucket via @setu-ts/cloudflare-plugin instead; this package has no R2 implementation.

Links:

• README
• API Reference

@setu-ts/service-discovery-plugin

Purpose: Service discovery for microservices.

Capability Token: CAPABILITIES.SERVICE_DISCOVERY

Runtime Compatibility:

Providers:

• Static
• Consul
• Kubernetes
• DNS-SRV

Links:

• README
• API Reference

@setu-ts/http-security-plugin

Purpose: Security middleware (CORS, headers, CSRF, rate limiting).

Capability Token: N/A (middleware-only)

Runtime Compatibility:

Features:

• CORS
• Security headers
• CSRF protection
• Rate limiting
• IP security

Links:

• README
• API Reference

Tooling

@setu-ts/cli

Purpose: Command-line interface for scaffolding and code generation.

Runtime Compatibility:

The table describes the importable package. The setu command itself is a Node program (Node 22 or later), published to npm with a bin; --runtime scaffolds projects for all four runtimes, Node by default.

Commands:

• setu new <name> - Create a new project (--template rest|microservice|class-based|full-stack, --style functional|class-based, --runtime node|deno|bun|cloudflare-workers, Node by default); --style class-based opts into decorators and dependency injection together on rest and microservice, and --template class-based is a byte-identical alias of --template rest --style class-based
• setu new <name> --workspace - Create a monorepo root (--port, --transport)
• setu generate <type> <name> - Generate code; 16 schematics, every one except guard, migration and (in a functional project) service and job wired into a registration site with no edit to a file you own
• setu generate app <name> - Add a service to a workspace, allocating its port and registering it in every sibling’s discovery map
• setu commands - List the commands this project’s plugins provide

Installation:

npx @setu-ts/cli new my-app
npm install --global @setu-ts/cli

Links:

• CLI Guide
• README
• API Reference

@setu-ts/create

Purpose: The npm create @setu-ts entry point — setu new with the caller’s arguments.

Runtime Compatibility:

The table describes the importable package (createArgs). The create executable is run by npm create on Node, and accepts exactly what setu new accepts.

Installation:

npm create @setu-ts my-app -- --template rest

Links:

• README
• API Reference

@setu-ts/sdk

Purpose: Client SDK for consuming Setu-TS applications.

Runtime Compatibility:

Features:

• HTTP client with auth interceptors
• Resilience (retry, circuit breaker, rate limit)
• OpenAPI code generation

Links:

• README
• API Reference

@setu-ts/testing

Purpose: Testing utilities for Setu-TS applications.

Runtime Compatibility:

Utilities:

• createTestApp() - Test application factory
• inject() - Test request injection
• createMockPlugin() - Mock plugin creator

Links:

• README
• API Reference

Starters

@setu-ts/rest-starter

Purpose: Opinionated REST API composition library.

Runtime Compatibility:

Includes: Runtime, Logger, Config, Validation, Exceptions, DI, Decorators, Auth, HTTP Security, OpenAPI, Health, Metrics.

Links:

• README
• API Reference

@setu-ts/microservice-starter

Purpose: Opinionated microservice composition library.

Runtime Compatibility:

Includes: All REST starter plugins + Messaging, Queue, Resilience, Telemetry, Service Discovery.

Links:

• README
• API Reference

@setu-ts/full-stack-starter

Purpose: Opinionated full-stack (SSR) composition library.

Runtime Compatibility:

Includes: All REST starter plugins + React Router, Session, Database.

Links:

• README
• API Reference

Notes

• Workers Compatibility: Packages marked ✅ for Workers run on the platform. Packages with HTTP-only providers (mail, storage, notification) work when configured with HTTP-based backends.
• Provider Limitations: Some packages have providers that are not Workers-compatible (e.g., SMTP for mail, raw sockets for messaging). Check individual package documentation.
• Runtime Detection: Use detectRuntime() from @setu-ts/runtime to conditionally enable features based on the runtime.