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

未关闭
#347 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
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 分钟
30 天内合并 PR
34

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

prisma/prisma-cli 的其他 Issue

查看 prisma/prisma-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。