Quickstart docs suggest `pnpm dlx tsc --init` / `yarn dlx tsc --init` which fetch the wrong npm package

[fuuuc]

Bug description

In the Prisma Postgres Quickstart, the "Initialize a TypeScript project" section recommends:

# pnpm
pnpm init
pnpm add typescript tsx @types/node --save-dev
pnpm dlx tsc --init          # ← problematic

# yarn
yarn init
yarn add typescript tsx @types/node --dev
yarn dlx tsc --init           # ← problematic
The problem: pnpm dlx and yarn dlx always fetch the package from the npm registry — they never check locally installed packages. The npm package named tsc is not the TypeScript compiler — it is a deprecated placeholder package (https://www.npmjs.com/package/tsc) (v2.0.4, last updated 2022, ~670k downloads/week mostly from accidental use) that prints "This is not the tsc command you are looking for".
Since typescript was just installed in the previous step, the correct command would be:
pnpm tsc --init   # runs the local node_modules/.bin/tsc
This does not affect the npm and bun tabs, because npx and bunx check node_modules/.bin/ first before falling back to the registry.
To reproduce
mkdir repro && cd repro
pnpm init
pnpm add typescript tsx @types/node --save-dev
pnpm dlx tsc --init
# → "This is not the tsc command you are looking for"
Expected behavior
pnpm dlx tsc --init should invoke the real TypeScript compiler (from the typescript package) and create a tsconfig.json.
Suggested fix
Replace pnpm dlx tsc --init with pnpm tsc --init and yarn dlx tsc --init with yarn tsc --init in the quickstart documentation.
Environment
- Doc URL: https://www.prisma.io/docs/prisma-orm/quickstart/prisma-postgres
- pnpm version: 11.12.0
- pkg tsc version: 2.0.4 (deprecated, no relation to typescript)

[fuuuc]

Suggestion: replace all pnpm dlx <cmd> with pnpm <cmd> when the package is already installed

Beyond the tsc name collision issue, there's a broader concern: pnpm dlx and yarn dlx always fetch from the registry — they never check locally installed packages. Throughout the quickstart, packages like typescript, prisma, tsx are installed via pnpm add in earlier steps, but later steps use pnpm dlx which ignores the local installation and downloads from npm every time.

Current command	Issue	Suggested fix
pnpm dlx tsc --init	Downloads wrong package (name collision)	pnpm tsc --init
pnpm dlx prisma	No error, but downloads a package already installed locally	pnpm prisma
pnpm dlx prisma init ...	Same	pnpm prisma init ...
pnpm dlx prisma migrate dev ...	Same	pnpm prisma migrate dev ...
pnpm dlx prisma generate	Same	pnpm prisma generate
pnpm dlx tsx script.ts	Same	pnpm tsx script.ts

Note: create-db is a valid use of pnpm dlx since it's typically not a project dependency. The same applies to bunx in the bun tabs.

The root cause: npx checks node_modules/.bin/ first and falls back to the registry only when the command is not found locally. But pnpm dlx / yarn dlx always go to the registry, even when the package is already installed. For prisma and tsx this works (correct package), but for tsc it hits the deprecated placeholder package and breaks entirely.

The fix is straightforward: use pnpm <cmd> (which runs from node_modules/.bin/) instead of pnpm dlx <cmd> for packages already added as dependencies. This applies to all package managers consistently:

• pnpm dlx → pnpm (or pnpm exec)
• yarn dlx → yarn

This also makes the quickstart example more consistent with real-world usage, where developers typically run locally installed CLI tools directly.