init: when no Prisma package is installed, say what to run next

オープン
#347 コメント 1 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
72/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
cli

調査の方向性

Start with docs/product/output-conventions.md, which describes the no-packages empty state. Then trace skillsOutcome() in packages/cli/src/commands/init.ts and the human and JSON next-action output; the issue says no tests are named. Done means adding the three proposed actions after npm install for no-packages in both outputs, while leaving the other outcomes unchanged.

索引モデルが issue の本文から書いたものです。

説明

enhancement

What happens

In a project with no Prisma package installed, prisma init sets up the skills hook and the config, then ends at the empty state. npx -y prisma@latest init --yes --format human in a directory with only a package.json (8.0.0-rc.22, 2026-10-12):

✔ Added "postinstall": "prisma skills sync || exit 0" to package.json.
✔ Added "prisma": "8.0.0-rc.22" to devDependencies in package.json.
✔ Created prisma.config.ts with skills: { agents: ["claude", "cursor", "agents", "devin"] }.
ℹ No Prisma packages with agent skills are installed.

project:  …/init-nopkg2
check:    enabled

→ Install the added prisma dev dependency: npm install

The JSON result has skills.outcome: "no-packages" and one next action (npm install). skillsOutcome() in packages/cli/src/commands/init.ts returns no-packages, and nothing attaches a next step to it.

npx prisma init is the command people and coding agents type from memory when they start a project. In this state they have a config and a hook, but nothing says how to get the ORM, a database, or hosting. An agent reading this output has no next command to run.

Proposal

When the skills outcome is no-packages, add three next actions after the install step, in both human and JSON output:

  1. run-command, prisma orm init, label: "Set up Prisma ORM in this project"
  2. run-command, npx create-db@latest, label: "No database yet? npx create-db@latest creates a temporary Prisma Postgres database and prints its URL; it is deleted after 24 hours unless you claim it."
  3. user-choice, label: "To host the app: prisma deploy module.ts deploys a Prisma Composer (Early Access) app to Prisma Compute after prisma auth login and a build: https://www.prisma.io/docs/compute/getting-started"

The create-db and deploy strings are the same ones proposed for prisma orm init in prisma/orm#30688, so the two commands agree. The other outcomes (synced, up-to-date, no-agents, no-skills, failed, skipped) stay as they are.

This repo is document-driven, so the first change would be to docs/product/output-conventions.md, which describes the no-packages empty state (No Prisma packages with agent skills are installed.). I can open that docs PR, and then the code and tests, if you agree with the direction.

Not this issue

A project whose package.json pins Prisma 5 or 7 is a separate problem: there, npx prisma init runs the version 8 CLI and writes a postinstall hook the pinned CLI cannot run. This issue is only about a project with no Prisma package.

@wmadden, does this fit how you want init to end?

主要言語
TypeScript
スター
25
フォーク
4
平均マージ
18時間 22分
マージ済み PR(30日)
34

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

prisma/prisma-cli のほかの issue

prisma/prisma-cli の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。