chore(core): add build:fast script

[NathanFlurry]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivetkit-serverless	Ready	Preview	Comment	Oct 5, 2025 10:01pm

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore(core): add support for auto-configuring serverless #1356 : 2 dependent PRs (#1352 , #1357 )
• chore(core): add build:fast script #1355 👈 (View in Graphite)
• feat(core): support running engine #1353
• fix(example-deno): fix check-types #1351
• chore(core): simplify config #1350
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

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.

[claude]

Claude finished @NathanFlurry's task —— View job

---

PR Review: Add build:fast script

Todo List:

• Read and analyze all changed files
• Review package.json changes
• Review turbo.json configuration changes
• Review tsup.base.ts changes
• Analyze build:fast implementation
• Provide comprehensive feedback

---

Code Review Feedback

This PR introduces a build:fast script that skips TypeScript declaration file generation to speed up builds during development. Overall, this is a solid implementation with good design decisions.

✅ Strengths

1. Clear Purpose: The fast build option serves a legitimate need - skipping expensive DTS generation during development iterations
2. Proper Environment Variable Handling: Uses FAST_BUILD=1 environment variable pattern which is conventional and clear
3. Consistent Implementation: The environment variable is properly propagated through Turbo's task configuration in both root and package-specific turbo.json files
4. Maintains Build Quality: Only skips DTS generation, keeping other important build steps like sourcemaps, splitting, and cleaning
5. Good Documentation: Comment in tsup.base.ts clearly explains why DTS is skipped (// DTS takes the longest time, so we skip it if doing a fast build)

🔧 Code Quality

tsup.base.ts:3: Clean environment variable reading pattern

const FAST_BUILD = process.env.FAST_BUILD === "1";

tsup.base.ts:12-19: Good conditional logic for DTS generation with proper TypeScript configuration when enabled

Turbo Configuration: Properly declares FAST_BUILD as an environment input in both turbo.json files, ensuring cache invalidation works correctly

🚀 Performance Considerations

• Positive Impact: Skipping DTS generation will significantly reduce build times during development
• Cache Efficiency: Turbo will properly cache builds based on the FAST_BUILD environment variable
• No Runtime Impact: Changes only affect build-time, not runtime performance

🔒 Security Assessment

• Low Risk: Environment variable usage is safe and standard
• No Sensitive Data: No secrets or sensitive information exposed
• Build-time Only: Changes don't affect runtime security posture

🧪 Test Coverage

• No Test Changes Needed: This is a build optimization that doesn't require new tests
• Existing Tests Should Pass: Fast builds should still produce functionally equivalent output (minus DTS files)

📝 Minor Suggestions

1. Documentation: Consider adding a comment in package.json explaining when to use build:fast vs build
2. Naming Consistency: The naming is good and follows conventional patterns

🎯 Recommendations

1. Consider Adding to README: Document the new build:fast script in development documentation
2. CI/CD Consideration: Ensure production builds continue using the full build command, not build:fast

✅ Overall Assessment

This is a well-implemented feature that addresses a real developer experience pain point. The code is clean, follows established patterns, and maintains build quality while improving development iteration speed. No blocking issues identified.

Approval Status: ✅ Ready to merge (pending any CI checks)

---

[pkg-pr-new]

More templates

• example-ai-agent
• example-better-auth-external-db
• chat-room
• example-cloudflare-workers
• example-cloudflare-workers-hono
• example-counter
• example-crdt
• example-database
• example-deno
• example-sqlite
• example-elysia
• example-express
• example-game
• example-hono
• example-hono-react
• example-kitchen-sink
• example-next-js
• example-rate
• example-raw-fetch-handler
• example-raw-websocket-handler-proxy
• example-react
• starter
• example-stream
• example-sync
• example-tenant
• example-trpc

@rivetkit/actor

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

@rivetkit/cloudflare-workers

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

@rivetkit/core

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

@rivetkit/db

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

commit: 99248b3

[claude]

Claude finished @NathanFlurry's task —— View job

---

Reviewing PR: Add build:fast script

Todo List:

• Read and analyze all changed files
• Review package.json changes
• Review turbo.json configuration changes
• Review tsup.base.ts changes
• Analyze build:fast implementation
• Provide comprehensive feedback

---

Code Review Feedback

This PR introduces a build:fast script that skips TypeScript declaration file generation to speed up builds during development. Overall, this is a solid implementation with good design decisions.

✅ Strengths

1. Clear Purpose: The fast build option serves a legitimate need - skipping expensive DTS generation during development iterations
2. Proper Environment Variable Handling: Uses FAST_BUILD=1 environment variable pattern which is conventional and clear
3. Consistent Implementation: The environment variable is properly propagated through Turbo's task configuration in both root and package-specific turbo.json files
4. Maintains Build Quality: Only skips DTS generation, keeping other important build steps like sourcemaps, splitting, and cleaning
5. Good Documentation: Comment in tsup.base.ts clearly explains why DTS is skipped (// DTS takes the longest time, so we skip it if doing a fast build)

🔧 Code Quality

tsup.base.ts:3: Clean environment variable reading pattern

const FAST_BUILD = process.env.FAST_BUILD === "1";

tsup.base.ts:12-19: Good conditional logic for DTS generation with proper TypeScript configuration when enabled

Turbo Configuration: Properly declares FAST_BUILD as an environment input in both turbo.json files, ensuring cache invalidation works correctly

🚀 Performance Considerations

• Positive Impact: Skipping DTS generation will significantly reduce build times during development
• Cache Efficiency: Turbo will properly cache builds based on the FAST_BUILD environment variable
• No Runtime Impact: Changes only affect build-time, not runtime performance

🔒 Security Assessment

• Low Risk: Environment variable usage is safe and standard
• No Sensitive Data: No secrets or sensitive information exposed
• Build-time Only: Changes don't affect runtime security posture

🧪 Test Coverage

• No Test Changes Needed: This is a build optimization that doesn't require new tests
• Existing Tests Should Pass: Fast builds should still produce functionally equivalent output (minus DTS files)

📝 Minor Suggestions

1. Documentation: Consider adding a comment in package.json explaining when to use build:fast vs build
2. Naming Consistency: The naming is good and follows conventional patterns

🎯 Recommendations

1. Consider Adding to README: Document the new build:fast script in development documentation
2. CI/CD Consideration: Ensure production builds continue using the full build command, not build:fast

✅ Overall Assessment

This is a well-implemented feature that addresses a real developer experience pain point. The code is clean, follows established patterns, and maintains build quality while improving development iteration speed. No blocking issues identified.

Approval Status: ✅ Ready to merge (pending any CI checks)

---

[claude]

Claude finished @NathanFlurry's task —— View job

---

Claude finished @NathanFlurry's task —— View job

---

PR Review: Add build:fast script

Todo List:

• Read and analyze all changed files
• Review package.json changes
• Review turbo.json configuration changes
• Review tsup.base.ts changes
• Analyze build:fast implementation
• Provide comprehensive feedback

---

Code Review Feedback

This PR introduces a build:fast script that skips TypeScript declaration file generation to speed up builds during development. Overall, this is a solid implementation with good design decisions.

✅ Strengths

1. Clear Purpose: The fast build option serves a legitimate need - skipping expensive DTS generation during development iterations
2. Proper Environment Variable Handling: Uses FAST_BUILD=1 environment variable pattern which is conventional and clear
3. Consistent Implementation: The environment variable is properly propagated through Turbo's task configuration in both root and package-specific turbo.json files
4. Maintains Build Quality: Only skips DTS generation, keeping other important build steps like sourcemaps, splitting, and cleaning
5. Good Documentation: Comment in tsup.base.ts clearly explains why DTS is skipped (// DTS takes the longest time, so we skip it if doing a fast build)

🔧 Code Quality

tsup.base.ts:3: Clean environment variable reading pattern

const FAST_BUILD = process.env.FAST_BUILD === "1";

tsup.base.ts:12-19: Good conditional logic for DTS generation with proper TypeScript configuration when enabled

Turbo Configuration: Properly declares FAST_BUILD as an environment input in both turbo.json files, ensuring cache invalidation works correctly

🚀 Performance Considerations

• Positive Impact: Skipping DTS generation will significantly reduce build times during development
• Cache Efficiency: Turbo will properly cache builds based on the FAST_BUILD environment variable
• No Runtime Impact: Changes only affect build-time, not runtime performance

🔒 Security Assessment

• Low Risk: Environment variable usage is safe and standard
• No Sensitive Data: No secrets or sensitive information exposed
• Build-time Only: Changes don't affect runtime security posture

🧪 Test Coverage

• No Test Changes Needed: This is a build optimization that doesn't require new tests
• Existing Tests Should Pass: Fast builds should still produce functionally equivalent output (minus DTS files)

📝 Minor Suggestions

1. Documentation: Consider adding a comment in package.json explaining when to use build:fast vs build
2. Naming Consistency: The naming is good and follows conventional patterns

🎯 Recommendations

1. Consider Adding to README: Document the new build:fast script in development documentation
2. CI/CD Consideration: Ensure production builds continue using the full build command, not build:fast

✅ Overall Assessment

This is a well-implemented feature that addresses a real developer experience pain point. The code is clean, follows established patterns, and maintains build quality while improving development iteration speed. No blocking issues identified.

Approval Status: ✅ Ready to merge (pending any CI checks)

---

[graphite-app]

Merge activity

• Oct 6, 7:40 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Oct 6, 7:41 PM UTC: CI is running for this pull request on a draft pull request (#1360) due to your merge queue CI optimization settings.
• Oct 6, 7:42 PM UTC: Merged by the Graphite merge queue via draft PR: #1360.