Preview feature feedback: Node-API support (`nApi`)

Please share your feedback about the nApi functionality released in v2.20.0 in this issue.

• If you encounter a bug, please open a bug report in this repo.
• If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.

If you have any questions, don’t hesitate to ask them in the #prisma-client channel in the Prisma Slack.

Known Limitations

• (Resolved) You can’t have more than one instance of the Prisma Client yet, so this will not work properly:

  const prisma1 = new PrismaClient()
  const prisma2 = new PrismaClient()
  

• (Resolved) Currently, logging queries does not work with Node-API and Jest (Issue). For example, the following will not output any query logs. (Note: This seems to only be the case when using jest)

  const prisma = new PrismaClient({
    log: ['query']
  })
  

• (Resolved) Node-API libraries do not work with process mocking of Jest (issue)
• Node-API does not work on M1 ARM Macs, Apple Silicon (issue)
• Node-API does not work on 32bit Node (issue)

[k-sae]

Originally posted here: #5792.

I had a major performance drawback when I was migrating from sequelize and seems the nApi solved it for me. Here are the details:

Environment

os: Linux (5.10.42-1-MANJARO)
DB: MySQL (10.4.19-MariaDB)
Node: v16.3.0
prisma: 2.25

Prisma schema:

model employees {
  emp_no       Int              @id
  birth_date   DateTime         @db.Date
  first_name   String           @db.VarChar(14)
  last_name    String           @db.VarChar(16)
  gender       employees_gender
  hire_date    DateTime         @db.Date
}

DB: employees_db

Code:

for (let index = 0; index < 2000; index++) {
    const employees = await prisma.employees.findMany({
      take: 100
    })
}

Results:

prisma: 42.497s
nApiPrisma: 6.146s

Full code here: https://github.com/k-sae/employees_prisma

[pimeys]

Throughput solved in latest dev.