Vitest picks the wrong index from prisma package.json

[garth]

Prisma generates a package.json like this:

{
  "name": ".prisma/client",
  "main": "index.js",
  "types": "index.d.ts",
  "browser": "index-browser.js"
}

Vitest is configured for node testing:

/// <reference types="vitest" />
import { defineConfig } from 'vite'

export default defineConfig({
  test: {
    environment: 'node',
  },
  esbuild: {
    platform: 'node',
  },
})

When running unit tests vitest picks the browser entry point from the generated prisma package.json.

Is this behaviour by design, I would have expected it to pick the index pointed to by main when the node environment is configured?

[sheremet-va]

This is Vite bug, it will be fixed in the next Vite and Vitest version

[PiotrJander]

Is there an issue to track this?