Reproduce potential Wasm bundling issue on `prisma migrate deploy`

When running prisma migrate deploy, some users faced the following error:

Error: ENOENT: no such file or directory, open '/home/site/wwwroot/node_modules/.bin/prisma_fmt_build_bg.wasm'
    at Object.openSync (node:fs:585:3)
    at Object.readFileSync (node:fs:453:35)
    at ../../node_modules/.pnpm/@prisma+prisma-fmt-wasm@4.4.0-66.f352a33b70356f46311da8b00d83386dd9f145d6/node_modules/@prisma/prisma-fmt-wasm/src/prisma_fmt_build.js (/home/site/wwwroot/node_modules/.bin/prisma:12337:31)
    at __require (/home/site/wwwroot/node_modules/.bin/prisma:14:50)
    at Object.<anonymous> (/home/site/wwwroot/node_modules/.bin/prisma:86202:38)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/home/site/wwwroot/node_modules/.bin/prisma_fmt_build_bg.wasm'
}

• node: 16.14.2
• prisma: 4.4.0

[janpio]

Am I reading the gist correctly that this was the solution for the problem?

use node node_modules/prisma/build/index.js migrate deploy instead of prisma migrate deploy

[bchoate-jpg]

Can you shared your build pipeline maybe @bchoate-jpg?

The project is private but here’s the relevant portion of the build workflow:

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v3

      - name: Set up Node.js version
        env:
          NPM_TOKEN: '${{ secrets.NPM_TOKEN }}'
        uses: actions/setup-node@v3
        with:
          node-version: '16.x'
          cache: 'yarn'

      - name: yarn install, build, and test
        env:
          NPM_TOKEN: '${{ secrets.NPM_TOKEN }}'
        run: |
          yarn install --frozen-lockfile
          yarn run build
          yarn run test

      - name: yarn install for production
        env:
          NPM_TOKEN: '${{ secrets.NPM_TOKEN }}'
        run: |
          rm -rf node_modules
          yarn install --production --frozen-lockfile

      - name: Zip artifact for deployment
        run: zip release.zip ./* -r

      - name: Upload artifact for deployment job
        uses: actions/upload-artifact@v3
        with:
          name: node-app
          path: release.zip

The yarn run build command is running npx tsc -b server && react-scripts build.