chore: allow imports of database schema from expo package.json

[Durisvk]

Having the following setup:

• Mobile App
• TRPC
• API
• Prisma Client

Mobile app imports a type AppRouter from api package in a monorepo so that it's aware of the exposed API.
The API uses Prisma (and therefore relies on '@prisma/client' types).

Metro bundler with this setup it's very strict on the "exports" field in the package.json.
Resulting in the following error:

Error: No known conditions for "." specifier in "@prisma/client" package
  at e (/Users/jurajcarnogursky/ooo/reusable-repo/node_modules/resolve.exports/dist/index.js:1:25)
  at n (/Users/jurajcarnogursky/ooo/reusable-repo/node_modules/resolve.exports/dist/index.js:1:645)
  at Object.exports (/Users/jurajcarnogursky/ooo/reusable-repo/node_modules/resolve.exports/dist/index.js:1:1653)
  at getPathInModule (/Users/jurajcarnogursky/ooo/reusable-repo/node_modules/@expo/cli/src/start/server/metro/createJResolver.ts:209:28)
  at defaultResolver (/Users/jurajcarnogursky/ooo/reusable-repo/node_modules/@expo/cli/src/start/server/metro/createJResolver.ts:133:53)
 ...

Applying this fix into node_modules/@prisma/client/package.json solves the issue.

BTW even the node_modules/.prisma/package.json generated by your library has it correctly set up:

".": {
      "require": {
        "node": "./index.js",
        "edge-light": "./wasm.js",
        "workerd": "./wasm.js",
        "worker": "./wasm.js",
        "browser": "./index-browser.js",
        "default": "./index.js"
      },
      "import": {
        "node": "./index.js",
        "edge-light": "./wasm.js",
        "workerd": "./wasm.js",
        "worker": "./wasm.js",
        "browser": "./index-browser.js",
        "default": "./index.js"
      },
      "default": "./index.js"
      }

[CLAassistant]

All committers have signed the CLA.

[SevInf]

Thank you! We are ready to merge it, but we'd like to have a test for it. We can take care of it ourselves, but we need a way to reproduce the problem first. Would running metro on @prisma/client be enough?

[Durisvk]

Thank you! We are ready to merge it, but we'd like to have a test for it. We can take care of it ourselves, but we need a way to reproduce the problem first. Would running metro on @prisma/client be enough?

I'm unsure @SevInf, we have a full-blown Turborepo setup with multiple frontends, API (with prisma), expo mobile app.

I can try to extract the minimal setup but I'm quite busy lately and believe that setting it up from scratch will be easier. For now we're using patch-package to workaround it.