Skip to content

Prisma docs mix npm and yarn commands as a instruction for Initializing a Typescript project #7618

@ajeetchaulagain

Description

@ajeetchaulagain

Description

While following the Prisma documentation for initializing a TypeScript project, I noticed that the commands mix npm and yarn.

For example, when selecting the Yarn tab, the instructions show:

npm init -y
npm install typescript tsx @types/node --save-dev
yarn dlx tsc --init

Running npm install generates a package-lock.json, which conflicts with Yarn's dependency management (yarn.lock). Is this behavior intentional in the documentation, or would it make sense to align the commands with Yarn to avoid generating package-lock.json?

Image

Link to the docs - https://www.prisma.io/docs/prisma-orm/quickstart/prisma-postgres

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions