Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error While running prisma2 init hello-prisma on macOS mojave #823

Closed
rbidanta opened this issue Oct 22, 2019 · 3 comments
Closed

Error While running prisma2 init hello-prisma on macOS mojave #823

rbidanta opened this issue Oct 22, 2019 · 3 comments
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug.
Milestone

Comments

@rbidanta
Copy link

I am trying to initialize a prisma2 project using the prisma2 init hello-prisma on macOS Mojave 10.14.6

Node Version: 10.14.2
npm Version: 6.4.1

Here are the steps I performed:

  1. installed prisma2 using npm install -g prisma2
  2. ran prisma2 init hello-prisma to create a new project
  3. Chose starter kit -> GraphQL API -> sqlLite
  4. Error occurs while installing dependencies with npm install ...
➜  pocs prisma2 init hello-prisma

Preparing your starter kit: GraphQL API

✔  Downloading the starter kit from GitHub ...
✔  Extracting content to hello-prisma ...
⠏  Installing dependencies with: `npm install` ...
4  Preparing your database ...
5  Seeding your database with: `npm run seed` ...
 ERROR  Error during command execution

npm WARN deprecated @types/graphql@14.5.0: This is a stub types definition. graphql provides its own type definitions, so you do not need this installed.
npm WARN deprecated apollo-upload-server@7.1.0: Please migrate to https://npm.im/graphql-upload (see https://git.io/fADhl).
sh: yarn: command not found
npm WARN graphql-playground-middleware-lambda@1.7.12 requires a peer of aws-lambda@^0.1.2 but none is installed. You must install peer dependencies yourself.
npm WARN graphql-subscriptions@0.5.8 requires a peer of graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN apollo-server-core@1.4.0 requires a peer of graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN apollo-cache-control@0.1.1 requires a peer of graphql@0.10.x - 0.13.x but none is installed. You must install peer dependencies yourself.
npm WARN apollo-tracing@0.1.4 requires a peer of graphql@0.10.x - 0.13.x but none is installed. You must install peer dependencies yourself.
npm WARN graphql-extensions@0.0.10 requires a peer of graphql@0.10.x - 0.13.x but none is installed. You must install peer dependencies yourself.
npm WARN typescript-graphql@ No repository field.
npm WARN typescript-graphql@ No license field.

npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! @prisma/sdk@0.0.20 postinstall: `yarn download`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @prisma/sdk@0.0.20 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/rbidanta/.npm/_logs/2019-10-22T15_12_34_461Z-debug.log

PS: I have not installed yarn on my machine, since nowhere prisma2 says yarn to be a mandatory package manager. I would try to run this again with yarn installed

@divyenduz divyenduz added process/candidate bug/1-unconfirmed Bug should have enough information for reproduction, but confirmation has not happened yet. kind/bug A reported bug. labels Oct 22, 2019
@rbidanta
Copy link
Author

rbidanta commented Oct 22, 2019

Update: I installed Yarn, and the prisma2 init hello-prisma seems to have executed successfully. However I still feel that the error message should be more descriptive to why the error occurred.
We may want to add yarn as one of the prerequisites for prisma2 to run on macOS mojave

@pantharshit00
Copy link
Contributor

yarn shouldn't be a prerequisite for Prisma. I can confirm this bug.

@pantharshit00 pantharshit00 added bug/2-confirmed Bug has been reproduced and confirmed. and removed bug/1-unconfirmed Bug should have enough information for reproduction, but confirmation has not happened yet. labels Oct 22, 2019
@janpio janpio assigned nikolasburk and timsuchanek and unassigned nikolasburk Oct 28, 2019
@janpio janpio added this to the Preview 16 milestone Oct 28, 2019
@pantharshit00 pantharshit00 removed their assignment Oct 31, 2019
@timsuchanek
Copy link
Contributor

Fixed in latest alpha.
You can try it out with npm i -g prisma2@alpha.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests

6 participants