PrismaClientInitializationError is missing errorCode property

[shiba-sama]

Bug description

• According to the docs, the PrismaClientInitializationError type should have an errorCode property but I'm seeing undefined for a range of errors which have this type.
• Currently the workaround is to match on the exact error message string, but I assume that's not something the Prisma team wants.

How to reproduce

1. Create a vanilla Prisma project and connect it to a DB.
2. Produce various connection errors like wrong username or password or disconnect your DB.
3. Try to make a query from the Prisma client and catch the error.
4. Inspect whether the error is an instance of PrismaClientInitializationError.
5. Inspect the errorCode property and see if it's undefined.

Expected behavior

Would be preferable if Prisma docs had a list of error codes and the associated error.

Prisma information

This is a connection error issue which can be replicated on any toy schema.

Environment & setup

• MacOS & Ubuntu
• PostgreSQL 15
• Node 19

Prisma Version

4.13

[Weakky]

Hey @shiba-sama, thanks for reporting 🙏.

Internal note: It looks like a regression of #10229. Thing is, we already have a regression test for it, which seems to be testing exactly that.

[AndrewSouthpaw]

Thanks for the investigation so far, @Weakky! Just wanted to signal boost this, we ran into it as well. We can implement the workaround for now.

If we were to rely on the errorCode though and it had another regression, that could lead to production outages, so hopefully the mystery of the regression test not catching it can be resolved.

[SevInf]

I can confirm the issue on 5.1.1:

async function main() {
  const prisma = new PrismaClient({
    datasources: {
      db: { url: 'postgres://invalid:invalid@localhost:5432/invalid' },
    },
  })

  try {
    await prisma.user.findMany()
  } catch (error) {
    console.log(error.errorCode)
  }
}

Logs undefined

Important node: it does not happen with explicit $connect call, only with implicit one done by findMany. That explains while test mentioned above did not catch it.

Unitl it fixed, the workeraound is to call prisma.$connect() some time before you execute your first query.