Skip to content

fix(client): fix dynamic wasm imports for Next.js Middlewares / Vercel Edge in @prisma/client#24312

Merged
Jolg42 merged 3 commits intomainfrom
integration/client-dynamic-wasm-imports
May 29, 2024
Merged

fix(client): fix dynamic wasm imports for Next.js Middlewares / Vercel Edge in @prisma/client#24312
Jolg42 merged 3 commits intomainfrom
integration/client-dynamic-wasm-imports

Conversation

@jkomyno
Copy link
Copy Markdown
Contributor

@jkomyno jkomyno commented May 28, 2024

This PR impacts how the Wasm Query Engine is loaded with @prisma/client's conditional import maps.

In particular, this PR:

For additional context:

/integration


You can try this PR with the integration version: 5.15.0-integration-client-dynamic-wasm-imports.1.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented May 28, 2024

size-limit report 📦

Path Size
packages/client/runtime/library.js 179.82 KB (0%)
packages/client/runtime/library.d.ts 81 B (0%)
packages/client/runtime/binary.js 600.89 KB (0%)
packages/client/runtime/binary.d.ts 26 B (0%)
packages/client/runtime/edge.js 159.02 KB (0%)
packages/client/runtime/edge-esm.js 158.91 KB (0%)
packages/client/runtime/wasm.js 114.9 KB (0%)
packages/client/runtime/index-browser.js 33.77 KB (0%)
packages/client/runtime/index-browser.d.ts 89 B (0%)
packages/cli/build/index.js 2.09 MB (0%)
packages/client/prisma-client-0.0.0.tgz 2.93 MB (0%)
packages/cli/prisma-0.0.0.tgz 3.73 MB (0%)
packages/bundle-size/da-workers-libsql/output.tgz 857.88 KB (0%)
packages/bundle-size/da-workers-neon/output.tgz 934.82 KB (0%)
packages/bundle-size/da-workers-pg/output.tgz 953.39 KB (0%)
packages/bundle-size/da-workers-pg-worker/output.tgz 909.1 KB (0%)
packages/bundle-size/da-workers-planetscale/output.tgz 870.86 KB (0%)
packages/bundle-size/da-workers-d1/output.tgz 830.93 KB (0%)

@jkomyno jkomyno changed the title integration: fix dynamic wasm imports for Next.js Middlewares / Vercel Edge in @prisma/client fix(client): fix dynamic wasm imports for Next.js Middlewares / Vercel Edge in @prisma/client May 28, 2024
@jkomyno jkomyno added this to the 5.15.0 milestone May 28, 2024
@jkomyno jkomyno self-assigned this May 28, 2024
@jkomyno
Copy link
Copy Markdown
Contributor Author

jkomyno commented May 28, 2024

Note: there are currently some ecosystem-tests failures, notably in the *-vercel-nextjs-edgemw.
Looking e.g. at https://e2e-driver-adapters-neon-http-vercel-nextjs-edgemw-gmu6iti7n.vercel.app, it seems that the test app works, but some test assertions fail.

@jkomyno jkomyno marked this pull request as ready for review May 28, 2024 16:05
@jkomyno jkomyno requested a review from a team as a code owner May 28, 2024 16:05
@jkomyno jkomyno requested review from Jolg42 and removed request for a team May 28, 2024 16:05
@SevInf
Copy link
Copy Markdown
Contributor

SevInf commented May 28, 2024

ecosytem-tests failure could be a flake, although i haven't seen this one before. Restarted the test for now.

Copy link
Copy Markdown
Contributor

@SevInf SevInf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but let's figure this ecosystem-tests failure before merging

@Jolg42
Copy link
Copy Markdown
Contributor

Jolg42 commented May 29, 2024

Note: the failures look unrelated to this PR because the default branch shows the same failures
https://github.com/prisma/ecosystem-tests/actions/runs/9286333431

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incompatibility with NextJS app dir, CloudFlare Pages and D1

4 participants