`prisma2 init` does not find `ts-node` when using starter kit "GraphQL API (+ Auth)"

Using Prisma 2 version: prisma2@2.0.0-preview-9.1, binary version: bbbeff6f84b408e534ebd866bfd378748e6d6611

When running prisma2 init with the GraphQL API (+ Auth)starter kit I came across the following error. I assume that the npm install did not install everything:

...

✔  Downloading the starter kit from GitHub ...

Preparing your starter kit: GraphQL API (+ Auth)

✔  Downloading the starter kit from GitHub ...
✔  Extracting content to prisma2preview91 ...
✔  Installing dependencies with: `npm install` ...
✔  Preparing your database ...
⠼  Seeding your database with: `npm run seed` ...
 ERROR  Error during command execution

sh: ts-node: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! graphql-auth@ seed: `ts-node prisma/seed.ts`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the graphql-auth@ seed 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/nickreynke/.npm/_logs/2019-09-02T17_20_11_738Z-debug.log

After running a npm i I could run npm run seed successfully.

[divyenduz]

I can still reproduce this with alpha.216. At least with the create folder feature of init.

prisma2 init <folder>

---

Note that the workaround of manually running npm install in the project still works.

[timsuchanek]

Fixed in the latest alpha.