Fix edge wasm handling during deploy (#40625)
This fixes the WASM handling for edge during deploy as the sandbox context won't be present so we should keep this restricted to dev. No additional tests were added as our existing tests caught this. x-ref: https://github.com/vercel/next.js/pull/39539 Fixes: https://github.com/vercel/next.js/actions/runs/3049403049/jobs/4915784368 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md`
Showing
Please
register
or
sign in
to comment