[Yumihariii]

Summary

prisma --version only prints the version string, so when a project runs a hoisted or global prisma you cannot tell which installation is actually executing. This makes the "Output path of current Prisma in -v" request from #7771 impossible to diagnose.

This PR makes the CLI report the absolute path of the executed prisma binary in the version output:

• human output now includes a Path: <absolute path> line (mirroring how yarn shows the resolved binary path);
• json output (--format json) adds a path field alongside version in the result envelope.

Implementation

The --version command is settled by @prisma/cli-engine's settleVersion. I patched that package via pnpm.patchedDependencies to resolve and print the executed binary path from process.argv[1] (resolved through symlinks with realpathOr). The existing --version --format json contract is unchanged — the new path field is additive.

Verification

• node dist/bin.mjs --version → 8.0.0-rc.14 + Path: /…/cli/dist/bin.mjs
• node dist/bin.mjs --version --format json → { "version": "8.0.0-rc.14", "path": "/…/cli/dist/bin.mjs" }
• pnpm vitest run test/version.test.ts → 1 passed

Closes #7771.

Summary by CodeRabbit

• New Features
  • Version output now includes the resolved path of the current executable when available. In human-readable output, the path appears after the version; in JSON output, it is provided as a path field.
  • When the executable path is unavailable, the version is still displayed and the path is omitted from both output formats. This keeps version information available even when no executable path can be determined.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

• Last reviewed commit: fc5d4b5
• Latest commit, not reviewed: 0026434

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review.

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: prisma/orm/.coderabbit.yml
• Review profile: CHILL
• Plan: Advanced
• Run ID: b31f44af-14fa-4b36-b244-4d0f5edc9de7

📥 Commits

Reviewing files that changed from the base of the PR and between 292da5f and fc5d4b5.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• patches/@prisma__cli-engine.patch

🚧 Files skipped from review as they are similar to previous changes (1)

• patches/@prisma__cli-engine.patch

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

Walkthrough

The root pnpm configuration registers a patch for @prisma/cli-engine. The patch adds the resolved executable path to text and JSON version output when available.

Changes: Version output path

Layer / File(s)	Summary
Configure and apply executable path reporting package.json, patches/@prisma__cli-engine.patch	The root pnpm configuration registers the cli-engine patch. The patch resolves the current executable path and adds it to text and JSON version results when available.

Priority: Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature · Severity of issue fixed: Low

Suggested reviewers: wmadden-electric

Merge Risk: Minimal · previous review fc5d4

The version output change appears mergeable with normal checks.

Architecture risk: Low · up to 292da

The change affects 2 systems.

Changed systems: package.json, patches

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — package.json (service) was modified; 1 changed file maps to changed impact.
• observed — patches (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in package.json: Added a patchedDependencies entry mapping @prisma/cli-engine to its patch file in the root pnpm configuration.
• observed — Modified behavior in patches/@prisma__cli-engine.patch: settleVersion now obtains the current executable path and includes it in human-readable and JSON version output when available. The new currentBinPath helper returns undefined if process.argv[1] is absent; otherwise, it resolves that entry with realpathOr.

🚥 Pre-merge checks | ✅ 5

✅ 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 clearly and concisely describes the main change: reporting the executed Prisma binary path in --version output.
Linked Issues check	✅ Passed	Issue #7771 is closed and provides historical context only. No active directly linked target remains. Therefore, no linked-issue coding requirements apply.
Out of Scope Changes check	✅ Passed	The changes are limited to the @prisma/cli-engine patch and its declaration in package.json. They add the executed binary path to human-readable and JSON version output. These changes match the st…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[Yumihariii]

@janpio this is still waiting on a human review — it's mergeable and CodeRabbit found nothing actionable. It's a small, backward-compatible change (adds a Path:/path line to the -v output). Would appreciate a look when you get a chance. Happy to adjust anything.

[Yumihariii]

Hi @janpio, just a gentle bump — I've rebased this onto the latest main and resolved the conflicts, so it's mergeable now. Would you have a moment to take a look when you get a chance?

[Yumihariii]

Hi @janpio, gentle bump — this PR is still blocked on human review (mergeable, awaiting a reviewer). I've kept it rebased on the latest main so it should be clean to review. Any chance you could take a look when you have a moment?

[janpio]

I don't work at Prisma any more, sorry. Please mention someone that does.

[Yumihariii]

Understood — that explains the radio silence, thanks for telling us @janpio.

@wmadden you've been actively merging in this repo, so one short ask: #7771 wants prisma -v to print the absolute path of the prisma binary that's actually executing (which install wins under hoisted/global setups). This PR does that through a pnpm.patchedDependencies patch on @prisma/cli-engine's settleVersion — a Path: line in the human output and a path field in --format json. Rebased onto current main, mergeable, DCO green, and the patch regenerates cleanly against the current engine dist.

We did notice #7771 is closed as completed — if that feature landed somewhere else already, just say so and we'll close this PR ourselves. If not, a look whenever convenient would help.