Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

browser build breaks in Vercel edge production #1238

Open
da7a90-backup opened this issue May 26, 2023 · 0 comments · May be fixed by #1285
Open

browser build breaks in Vercel edge production #1238

da7a90-backup opened this issue May 26, 2023 · 0 comments · May be fixed by #1285

Comments

@da7a90-backup
Copy link

da7a90-backup commented May 26, 2023

Expected Behavior

expect the browser build to work in the edge runtime's production environment using import * as _jimp from 'jimp' workaround mentioned in #1194 also with unstable_allowDynamic enabled but it doesn’t seem to have any effect on it.

Current Behavior

it works locally and in the preview staging environment but not in production

Failure Information (for bugs)

According to Nextjs docs Source Maps are disabled unless your provide a productionBrowserSourceMaps: true, flag which I haven't tested yet.

Steps to Reproduce

use jimp in a vercel edge function locally and try to push to production via github actions.

Context

  • Jimp Version:^0.22.8
  • Operating System: MacOS locally and Vercel Edge runtime in production
  • Node version: latest

Failure Logs

- warn Dynamic Code Evaluation (e. g. 'eval', 'new Function') not allowed in Edge Runtime
Learn More: https://nextjs.org/docs/messages/edge-dynamic-code-evaluation```
@hipstersmoothie hipstersmoothie linked a pull request Mar 28, 2024 that will close this issue
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 a pull request may close this issue.

1 participant