feat: add deno support, alt approach

[kt3k]

This is an alternative approach to #14250

This PR updates prisma generate command. When previewFeatures = ["denoDeploy"] is specified in the schema, then generate command outputs the client compatible with Deno and Deno Deploy.

---

Summary of changes (all changes only happen when previewFeatures = ["denoDeploy"] is specified):

• Updates the generated client scripts to fit to deno
• Generates runtime/edge-esm.js which is used by deno
• Shows the error message when output is not specified in generator client
• Shows the example which is suitable for deno (import ... from './client/edge.ts' instead of import ... from './client/edge')

[kt3k]

I believe the CI failures are caused by the flakiness of test cases. I found similar errors in main's CI

• The error in @prisma/client tests/functional/missing-env/tests.ts 1 2
• The error in @prisma/generator-helper src/__tests__/generatorHandler.test.ts 3

[kt3k]

@millsp Updated the PR. This branch now uses previewFeatures = ["denoDeploy"] and doesn't affect existing prisma clients. PTAL

Summary of changes (all changes only happen when previewFeatures = ["denoDeploy"] is specified):

• Updates the generated client scripts (edge.js and runtime/index.d.ts) to fit to deno
• Generates deno specific scripts (edge.ts (thin wrapper), deno-polyfill.js (small polyfill))
• Generates runtime/edge-esm.js which is used by deno
• Shows the error message when output is not specified in generator client
• Shows the example which is suitable for deno (import ... from './client/edge.ts' instead of import ... from './client/edge')

[kt3k]

BTW I currently can't build main branch (on my local machine) because of missingDependencies ["is-ci"] error in pnpm run build of packages/internals. ( I created this diff from b39cf85 )

[Jolg42]

@kt3k we recently removed the is-ci dependency from internals.
Though it should not be used there anymore, maybe try to get the branch up-to-date with main.
Make sure to run pnpm i at the root directory.

[kt3k]

I now see an error in my integration test setting (like ENOENT: no such file or directory, open '/path/to/prisma/reproductions/basic-sqlite/prisma/generated/client/deno/index.d.ts'. I'll address that tomorrow

[millsp]

I pinged you on slack about the deno folder, so that we can have a quick conversation about it.

[kt3k]

I now see an error in my integration test setting (like ENOENT: no such file or directory, open '/path/to/prisma/reproductions/basic-sqlite/prisma/generated/client/deno/index.d.ts'. I'll address that tomorrow

Addressed this issue. The generated client can make request to data proxy in my settings. It also can pass the type checking by deno's type checker (type completions of prisma client, models, etc are available).

Now the prisma generate creates directory /deno/, and deno specific files are created in it. The main entrypoint for deno deploy client is ${output}/deno/deploy.ts for now. I'm open to change it back to the root if we prefer it. What do you think?

[janpio]

(Sorry, I tried to resolve the conflicts and had messed up - so had to force push the previous state again. No changes.)

[janpio]

I don't like that deno previw is in the else. Can we rewrite this that this also reacts to isDenoPreview @millsp?

[janpio]

New engine to use with deno preview feature: 4.5.0-38.71723d0f37369be033e71bd7cd314749d8348f9f

[millsp]

Work continued here #15281

[millsp]

We've merged this work via #15281. Kudos to @kt3k, we're super thankful for your contribution and good work! 🥳 🎉

[kt3k]

@millsp So glad to see this landed! Thank you for your reviews and guidances!