feat: add ladle

[jog1t]

Description

Added Ladle component development environment to the frontend. This PR:

1. Adds Ladle as a dependency to the frontend package
2. Creates a Docker setup for building and serving the Ladle environment
3. Configures Railway deployment files for PR and staging environments
4. Adds a sample workflow component story
5. Updates .gitignore to exclude the Ladle build directory
6. Adds npm scripts for Ladle development and building

Ladle provides an isolated environment for developing and testing UI components, making it easier to build and maintain a consistent component library.

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Tested locally by running the Ladle development server and verifying that components can be viewed and interacted with in isolation.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4168 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Feb 19, 2026 at 2:29 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 16, 2026 at 4:39 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 16, 2026 at 4:39 pm
ladle	❌ Build Failed (View Logs)	Web	Feb 16, 2026 at 4:39 pm
mcp-hub	✅ Success (View Logs)	Web	Feb 10, 2026 at 9:04 pm

[jog1t]

• feat: add xyflow #4170 : 2 dependent PRs (#4172 , #4211 )
• feat: add ladle #4168 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Graphite Automations

"Test" took an action on this PR • (02/10/26)

1 assignee was added to this PR based on Kacper Wojciechowski's automation.

[claude]

PR Review: feat: add ladle

Summary

This PR adds Ladle as a component development environment for the frontend. The core additions are solid: a shared Vite config base, Ladle configuration, a Caddy server config, a Dockerfile, and Railway deployment config. Several issues need to be addressed before merging.

---

Blockers

1. Accidentally committed scripts/skill-evals/results/ files

The following files are unrelated to Ladle and appear to be accidentally committed agent evaluation artifacts:

• scripts/skill-evals/results/auth-flow/ (3 files)
• scripts/skill-evals/results/fill-form/ (3 files)
• scripts/skill-evals/results/js-counter/ (7 files, including raw agent.log)
• scripts/skill-evals/results/open-and-snapshot/ (3 files)
• scripts/skill-evals/results/react-counter/ (4 files)

These should be removed from this PR. If these results need to be committed, they belong in a separate PR. Consider adding scripts/skill-evals/results/ to .gitignore.

2. CMD removed from cloud.Dockerfile and inspector.Dockerfile

Both files had their final CMD ["caddy", "run", "--config", "/etc/caddy/Caddyfile"] line removed. The only remaining directive is ENTRYPOINT ["/docker-entrypoint.sh"]. If docker-entrypoint.sh passes $@ to caddy, containers will now start with no arguments. Please confirm that the entrypoint script hardcodes the caddy command and this removal is intentional.

---

Issues

3. @ladle/react placed in dependencies, not devDependencies

Ladle is a build/development tool and should be in devDependencies. The same applies to @xyflow/react if it was added solely for Ladle stories.

4. railway.cloud-staging.toml deleted without explanation

This file was removed with no mention in the PR description. Was cloud-staging intentionally retired? If so, please add a note. If not, this deletion is unintentional.

5. railway.ladle.toml has incomplete watchPatterns

The watch patterns only include /frontend/** and /pnpm-lock.yaml, but ladle.Dockerfile copies many additional directories that can change independently:

/engine/sdks/typescript/**
/rivetkit-typescript/packages/**
/shared/typescript/**
/examples/**

Changes to rivetkit or engine SDK code will not trigger a Railway rebuild. This matches the same issue in the existing cloud/inspector Railway configs; consider fixing all three.

6. Turbo build:ladle inputs are incomplete

The turbo.json entry for build:ladle does not list the Ladle-specific config files as inputs, so turbo will not invalidate the cache when they change:

 "build:ladle": {
     "dependsOn": ["^build"],
     "inputs": [
         "src/**",
         "tsconfig.json",
+        ".ladle/**",
+        "vite.base.config.ts",
         "package.json"
     ],

Similarly, build:cloud and build:inspector should include vite.base.config.ts in their inputs since they now depend on it via mergeConfig(baseViteConfig(), ...).

---

Minor / Suggestions

7. Placeholder story in workflow.stories.tsx

The only story exported is:

export const World = () => <div>World</div>;

This does not demonstrate the actual Workflow component. Either replace it with a real story or, if this is intentional scaffolding, add a comment explaining it is a placeholder pending component work.

8. frontend/.ladle/config.mjs has no story glob

The Ladle config only sets viteConfig. Adding an explicit stories glob makes discovery behavior predictable and avoids Ladle scanning the entire src/ tree:

export default {
  viteConfig: ".ladle/vite.config.ts",
  stories: "src/**/*.stories.{tsx,ts}",
};

9. ladle.Dockerfile copies frontend/public/examples/ twice

COPY frontend/ frontend/
COPY frontend/public/examples/ frontend/public/examples/  # redundant, already included above

The second COPY is a no-op since frontend/ is already copied in full. Remove the redundant line.

10. ladle.Dockerfile missing bash / entrypoint

The cloud and inspector Dockerfiles install bash and use a custom entrypoint script for runtime env-var substitution. The ladle Dockerfile skips this. Since Ladle is static and has no runtime env vars to substitute, this is likely fine, but a brief comment in the Dockerfile clarifying the intentional difference would help future readers.

---

What Looks Good

• The extraction of shared Vite config into vite.base.config.ts reduces duplication correctly and uses mergeConfig properly.
• Caddy config (Caddyfile.ladle) has correct security headers, gzip compression, aggressive caching for static assets, and SPA catch-all routing.
• Docker layer ordering is good: workspace files first, then package sources, then install, then build.
• The pnpm cache mount IDs are unique per Dockerfile, which is correct.

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• custom-serverless-vercel
• example-elysia
• example-elysia-vercel
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-hono-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• example-sqlite-raw-vercel
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc
• example-trpc-vercel

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@4168

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@4168

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@4168

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@4168

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@4168

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@4168

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4168

@rivetkit/traces

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/traces@4168

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4168

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4168

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4168

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4168

commit: 21d269f

[graphite-app]

Merge activity

• Feb 19, 11:17 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Feb 19, 11:18 PM UTC: CI is running for this pull request on a draft pull request (#4244) due to your merge queue CI optimization settings.
• Feb 19, 11:19 PM UTC: Merged by the Graphite merge queue via draft PR: #4244.