Seeding seems to swallow errors

[matthewmueller]

Bug description

Seeding seems to swallow runtime errors

How to reproduce

Given the following in prisma/seed.ts

import { PrismaClient, Color } from "@prisma/client"
import * as fs from "fs/promises"
const prisma = new PrismaClient()

async function main() {
  await prisma.$connect()
  const files = await fs.readdir("./zzzzz")   // doesn't exist
  console.log(files)
  }

main()
  .catch(console.error)
  .finally(() => prisma.$disconnect())

Note that the directory doesn't exist. I have a package.json with:

{
  "prisma": {
    "seed": "ts-node prisma/seed.ts"
  }
}

When I run npx prisma db seed:

npx prisma db seed    
Environment variables loaded from .env
Running seed command `ts-node prisma/seed.ts` ...

🌱  The seed command has been executed.

However when I run the command directly:

ts-node prisma/seed.ts
[Error: ENOENT: no such file or directory, scandir './zzzzz'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: './zzzzz'
}

Expected behavior

I'd expect to see the error from prisma seed and for it to fail

Prisma information

Environment & setup

• OS: Mac OS
• Database: Postgres
• Node.js version: v14.16.0

Prisma Version

Environment variables loaded from .env
prisma                  : 3.0.2
@prisma/client          : 3.0.2
Current platform        : darwin
Query Engine (Node-API) : libquery-engine 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : 2452cc6313d52b8b9a96999ac0e974d0aedf88db
Studio                  : 0.423.0