ENG-428 Cross-platform build script in packages/database

[maparent]

Summary by CodeRabbit

• Chores
  • Updated the build process for the database package to use a single TypeScript script, streamlining setup and migration steps. No changes to user-facing features.

[linear]

ENG-428 Cross Platform solution for package/repo build

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
discourse-graph	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 9, 2025 4:41pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

The build process for the database package was refactored. The npm build script now directly runs a new TypeScript script, build.ts, which handles starting Supabase, applying migrations, and generating TypeScript types, but only when not running in the Vercel environment. The logic previously embedded in the shell script is now centralized in this TypeScript script.

Changes

File(s)	Change Summary
packages/database/package.json	Updated the build script to run tsx scripts/build.ts instead of a shell conditional with Supabase commands.
packages/database/scripts/build.ts	Added a new TypeScript script that conditionally starts Supabase, applies migrations, and generates types.

Poem

In the warren where databases grow,
A new script hops in, ready to go!
No more shell tricks, just TypeScript flair,
Supabase starts up with nary a care.
Migrations and types, all in one run—
The build is now simple, efficient, and fun!
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[maparent]

@CodeRabbit review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (3)

packages/database/scripts/build.ts (3)

1-2: Fix import formatting.

Missing space after comma in the import statement.

-import {writeFileSync} from "fs"
+import { writeFileSync } from "fs"

---

4-4: Use strict equality comparison.

Use !== instead of != for strict equality comparison to avoid type coercion issues.

-if (process.env.HOME != '/vercel') {
+if (process.env.HOME !== '/vercel') {

---

13-13: Consider using absolute path for output file.

The relative path 'types.gen.ts' may write to an unexpected location depending on the current working directory when the script is executed.

+import { join } from "path";
+import { dirname } from "path";
+import { fileURLToPath } from "url";
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const projectRoot = join(__dirname, '..');

-        writeFileSync('types.gen.ts', stdout);
+        writeFileSync(join(projectRoot, 'types.gen.ts'), stdout);

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 901e473 and 02e7823.

📒 Files selected for processing (2)

• packages/database/package.json (1 hunks)
• packages/database/scripts/build.ts (1 hunks)

🔇 Additional comments (1)

packages/database/package.json (1)

17-17: Good refactoring to improve maintainability.

Moving the conditional logic from shell script to TypeScript improves readability and maintainability. The change centralizes the build logic in a dedicated script file.

[mdroidian]

👍