Skip to content
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.

prisma2 generate always uses yarn even if you're using NPM in your project #561

Closed
matthewmueller opened this issue Mar 11, 2020 · 3 comments
Assignees
Labels
bug/2-confirmed We have confirmed that this is a bug. kind/bug A reported bug.
Milestone

Comments

@matthewmueller
Copy link
Contributor

If you're an NPM user, you'll get a package-lock.json and package.json. Running prisma2 generate does not pick up that we're using NPM and always uses yarn. This ends up creating both a package-lock.json file and a yarn.lock file.

Full repro here: #560

@matthewmueller matthewmueller added the bug/2-confirmed We have confirmed that this is a bug. label Mar 11, 2020
@Jolg42 Jolg42 added the kind/bug A reported bug. label Mar 11, 2020
@Jolg42 Jolg42 self-assigned this Mar 11, 2020
@Jolg42 Jolg42 added this to the Preview 24 New milestone Mar 11, 2020
@Jolg42
Copy link
Member

Jolg42 commented Mar 11, 2020

We may want to use https://github.com/sindresorhus/has-yarn in generate

@divyenduz divyenduz added process/candidate Candidate for next Milestone. and removed process/candidate Candidate for next Milestone. labels Mar 12, 2020
@janpio janpio added the process/candidate Candidate for next Milestone. label Mar 12, 2020
@divyenduz divyenduz modified the milestones: Preview 24 New, Preview 25 Mar 13, 2020
@divyenduz
Copy link

Related issue: #560

@Jolg42
Copy link
Member

Jolg42 commented Mar 17, 2020

fixed in alpha 920!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug/2-confirmed We have confirmed that this is a bug. kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests

4 participants