Prisma1: Running boilerplate install script... ✖ Unexpected token )

[hakimelek]

Bug Report

I was trying to setup my first time prisma project.

Current behavior
Breaking during prisma init right after the npm install during prisma init.

log:

[graphql create] Running boilerplate install script...
✖
Unexpected token )

Reproduction
npm install -g prisma
prisma init [project-name]

Choosing node-advanced and GraphQL server (incl. database & authen tication)

Expected behavior?
It should finish the install script

[timbaas]

Same here, breaks on src/index.js line 27 because of the comma after info:

26    },
27    info,
28  )

Node version 7.8.0

Edit: Seems to work on Node v8.9.4

[brandonmp]

ahh, glad i'm not alone

same problem on typescript-advanced, node 9.4

https://github.com/graphql-boilerplates/typescript-graphql-server/issues/152

[DevanB]

I opened a ticket in the React boilerplate, that will get patched in all other boilerplates. We should b checking node version.
https://github.com/graphql-boilerplates/react-fullstack-graphql/issues/220

[marktani]

Thanks @DevanB!

@hakimelek @brandonmp can you confirm that a more recent Node version works for you, too? 🙂

[brandonmp]

my issue was in node 9.4 😕

[DevanB]

Hmmm, @brandonmp can you recreate it?

[marktani]

Hey @brandonmp, your issue looks unrelated and more akin to this one.

[marktani]

This seems resolved :slightly_smiling_face: I'll close this due to inactivity. Please create a new issue if you are experiencing a similar problem.

[KingIdee]

Hi! I'm still experiencing the same issue
prisma/1.5.1 (linux-x64) node-v7.10.1

[marktani]

@KingIdee, please upgrade your node version to a more recent one.

[lucfranken]

First experience with Prisma, same issue. The installer should check the nodejs version or raise a warning. Now as a first time user you need to Google an error before you can even test it.

The reason why many have older versions could for example be that they use Meteor which has pinned NodeJS versions. That leaves your global version untouched. Not sure if that's something your team may encounter yourself since for your work it's a regular thing likely to update node.