fix: Use pnpm exec instead of pnpm dlx (#2960)

[KATO-Hiro]

close #2960

Summary by CodeRabbit

• Chores

  • Updated database seed and studio startup scripts to run via pnpm exec tsx for more reliable TypeScript execution and improved alias compatibility.
  • Added tsx as a development dependency to support the new workflow.

• Documentation

  • Added docs explaining the tooling change, migration rationale, usage instructions, and implementation notes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Switch Prisma seed execution from pnpm dlx vite-node to pnpm exec tsx. Add tsx as a devDependency and update package.json scripts (db:seed, db:studio). Add documentation describing rationale, alternatives considered, implementation details, and execution instructions.

Changes

Cohort / File(s)	Summary
Documentation docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md	New file explaining the decision to replace pnpm dlx vite-node with pnpm exec tsx, evaluation of alternatives (Node.js native TS support vs tsx), implementation notes (tsconfig/alias, peer-deps), Q&A, and usage instructions.
Configuration package.json	Updated scripts: db:seed → pnpm exec tsx ./prisma/seed.ts; db:studio → pnpm exec prisma studio. Added tsx v4.21.0 to devDependencies.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify accuracy of documentation regarding pnpm exec vs pnpm dlx behavior and the chosen approach.
• Confirm package.json script syntax and that tsx@4.21.0 is intended.

Poem

🐰 I hopped from dlx to exec with cheer,
pnpm now runs the versions near,
tsx tucked in my dev-time pack,
seeds sprout steady, no turning back,
thump, a tiny rabbit clap — hooray!

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: switching from pnpm dlx to pnpm exec commands in the codebase.
Linked Issues check	✅ Passed	The PR successfully implements the requirement from issue #2960 to replace pnpm dlx with pnpm exec for both seed and studio commands.
Out of Scope Changes check	✅ Passed	All changes are directly related to the objective of replacing pnpm dlx with pnpm exec; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch #2960

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 0fb5366 and 263af88.

📒 Files selected for processing (1)

• docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md

[grammar] ~11-~11: Ensure spelling is correct
Context: ...new projects, please consider using the builtin Vite one instead." 出典: [vite-node ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (1)

docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md (1)

1-141: Documentation comprehensively supports the PR objectives.

The document clearly explains the decision to switch from pnpm dlx to pnpm exec with solid technical reasoning, well-evaluated alternatives, and a helpful Q&A section. The structure is logical and the explanations are accurate. The content effectively documents why the change improves consistency between development and package.json pinned versions.

The static analysis tool flagged a potential spelling issue on line 11 regarding "builtin"—however, this is part of a direct quote from the vite-node repository and should remain as-is.

One note: The documentation explains in Q2 that tsx is available as a peer dependency from other packages, yet the AI summary mentions tsx is added as an explicit devDependency in package.json. If tsx was explicitly added as a devDependency (rather than relying on peer dependency resolution), you may want to update the Q2 explanation to reflect this change or clarify that both approaches work.

---

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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md (1)

33-33: Optional: Address markdown linting suggestions.

Minor markdown formatting improvements flagged by static analysis:

1. Line 33: Add a language identifier to the fenced code block (e.g., text` or shell`)
2. Lines 137-141: Convert bare URLs to markdown link syntax for consistency

Example for lines 137-141:

-- vite-node: https://github.com/vitest-dev/vitest
+- vite-node: [https://github.com/vitest-dev/vitest](https://github.com/vitest-dev/vitest)

These are purely stylistic and don't affect the documentation's clarity.

Also applies to: 137-141

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 703d1da and 0fb5366.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md (1 hunks)
• package.json (2 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md

[grammar] ~11-~11: Ensure spelling is correct
Context: ...new projects, please consider using the builtin Vite one instead." 出典: [vite-node ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🪛 markdownlint-cli2 (0.18.1)

docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md

33-33: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

137-137: Bare URL used

(MD034, no-bare-urls)

---

138-138: Bare URL used

(MD034, no-bare-urls)

---

139-139: Bare URL used

(MD034, no-bare-urls)

---

140-140: Bare URL used

(MD034, no-bare-urls)

---

141-141: Bare URL used

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: preview

🔇 Additional comments (3)

package.json (2)

27-28: LGTM! Script changes align with PR objective.

The switch from pnpm dlx to pnpm exec ensures these scripts use the versions specified in package.json rather than fetching the latest from the registry each time, improving consistency and speed.

---

68-68: Version 4.21.0 is valid and has no known security vulnerabilities.

tsx version 4.21.0 is the latest version, published 16 days ago, and has no known vulnerabilities. The explicit devDependency declaration is appropriate for version control.

docs/dev-notes/2025-12-17/use_pnpm_exec/plan.md (1)

1-141: Excellent documentation quality.

The documentation thoroughly explains the rationale for switching from vite-node to tsx, including:

• Historical context about vite-node deprecation
• Comparison of alternatives (Node.js built-in vs tsx)
• Clear Q&A addressing the differences between pnpm dlx and pnpm exec
• Implementation details with code examples

This will help future maintainers understand the decision and context.

[KATO-Hiro]

LGTM