Skip to content

Change package command from 'neondb' to 'get-db' for neon database setup - #667

Merged
AmanVarshney01 merged 1 commit into
AmanVarshney01:mainfrom
nitinmogalapalli:patch-1
Nov 3, 2025
Merged

AmanVarshney01 merged 1 commit into
AmanVarshney01:mainfrom
nitinmogalapalli:patch-1

Conversation

@nitinmogalapalli

@nitinmogalapalli nitinmogalapalli commented Nov 3, 2025 •

Copy link
Copy Markdown
Contributor

The package "neondb' has been renamed to 'get-db'.

Summary by CodeRabbit

  • Chores
    • Updated the CLI command used during Neon database initialization. All existing workflows and setup functionality remain unchanged, ensuring a consistent experience.

@vercel

vercel Bot commented Nov 3, 2025

Copy link
Copy Markdown

@nitinmogalapalli is attempting to deploy a commit to the Aman Varshney's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Nov 3, 2025 •

Copy link
Copy Markdown
Contributor

Walkthrough

The Neon database setup CLI command was updated from "neondb@latest" to "get-db@latest" in the neon-setup helper. This change updates the invoked package execution command while preserving all surrounding logic and error handling.

Changes

Cohort / File(s) Summary
Neon setup utilities
apps/cli/src/helpers/database-providers/neon-setup.ts
Updated package execution command from "neondb@latest --yes" to "get-db@latest --yes"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Single command string replacement with no logic or structural changes
  • Verify that "get-db@latest" provides equivalent functionality to "neondb@latest" for resource creation

Possibly related PRs

Poem

🐰 A rabbit hops from neondb to get-db's door,
Where setup scripts flow like never before,
One command swaps, the logic stays true,
thump thump ✨ Fresh databases brew!

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title directly and clearly describes the main change in the changeset. The title 'Change package command from 'neondb' to 'get-db' for neon database setup' accurately captures the primary modification, which involves switching the package execution command from 'neondb@latest' to 'get-db@latest' in the Neon setup flow. The title is specific, concise, and provides sufficient context for reviewers to understand the change at a glance.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4e168 and 093a3ba.

📒 Files selected for processing (1)
  • apps/cli/src/helpers/database-providers/neon-setup.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/convex_rules.mdc)

**/*.{ts,tsx}: Use Id from './_generated/dataModel' to type document ids (e.g., Id<'users'>)
Ensure Record key/value types align with validators (e.g., v.record(v.id('users'), v.string()) => Record<Id<'users'>, string>)
Be strict with types for document ids; prefer Id<'table'> over string
Use 'as const' for string literals in discriminated unions
When using Array and Record types, declare with explicit generic types (e.g., const arr: Array = ...)

**/*.{ts,tsx}: Use TypeScript type aliases instead of interface declarations.
Do not use explicit return types in TypeScript.

Files:

  • apps/cli/src/helpers/database-providers/neon-setup.ts
**/*.{js,jsx,ts,tsx,mjs,cjs}

📄 CodeRabbit inference engine (.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc)

**/*.{js,jsx,ts,tsx,mjs,cjs}: Do not use dotenv; Bun auto-loads .env
Use Bun.serve() for HTTP/WebSockets; do not use express
Use bun:sqlite for SQLite; do not use better-sqlite3
Use Bun.redis for Redis; do not use ioredis
Use Bun.sql for Postgres; do not use pg or postgres.js
Use built-in WebSocket; do not use ws
Prefer Bun.file over node:fs readFile/writeFile
Use Bun.$ instead of execa for shelling out

Files:

  • apps/cli/src/helpers/database-providers/neon-setup.ts
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/better-t-stack-repo.mdc)

Define functions using the standard function declaration syntax, not arrow functions.

Files:

  • apps/cli/src/helpers/database-providers/neon-setup.ts
🔇 Additional comments (1)
apps/cli/src/helpers/database-providers/neon-setup.ts (1)

136-136: The web search results do not provide information about get-db or neondb as npm packages. The search returned results about Neon's database service and documentation, where "neondb" is mentioned as a default database name (e.g., "Your Neon project comes with a ready-to-use Postgres database named neondb"), not as an npm package.

However, the npm view command succeeded for both packages, returning version 0.9.2 for each. This suggests both package names may exist on npm, but they're either obscure, scoped packages, or not easily discoverable through standard web searches.

Verify the package name and update user-facing messages for consistency.

The npm view command returns version 0.9.2 for both get-db and neondb, suggesting both packages exist. However, the package's purpose could not be verified through standard web searches. Additionally, the package command change creates an inconsistency: the code now references "get-db" but user-facing messages still reference "neondb":

  • Line 128: spinner message says "Creating Neon database using neondb..."
  • Line 148: error message says "Failed to create database with neondb"
  • Line 211: UI option label says "Quick setup with neondb"

Before merging, verify that:

  1. The get-db@latest package is the correct replacement and the rename is intentional
  2. Whether user-facing messages should also be updated to reference "get-db" for consistency, or if "neondb" is intentionally retained as the feature name while "get-db" is the implementation package

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@AmanVarshney01
AmanVarshney01 merged commit 3a9075f into AmanVarshney01:main Nov 3, 2025
@AmanVarshney01

Copy link
Copy Markdown
Owner

Thanks @nitinmogalapalli 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants