Vercel deployment errors

BCFCODE commented 3 weeks ago

Steps to reproduce

Link to live example: (required)

Steps: 1. 2. 3.

Current behavior

I can't deploy it to vercel! many errors occurred in logs

Expected behavior

Successfull vercel deployment

Context

No response

Your environment

This Edge Function has crashed.

Your connection is working correctly.

Vercel is working correctly.

500: INTERNAL_SERVER_ERROR Code: EDGE_FUNCTION_INVOCATION_FAILED ID: fra1:fra1::h9zmp-1729184723339-74f07fa7b9b9

If you are a visitor, contact the website owner or try again later. If you are the owner, learn how to fix the error and check the logs.

npx @mui/envinfo

 Braowser: Microsoft Edge
 System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 22.3.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.1 - ~\AppData\Local\pnpm\pnpm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3
    @emotion/styled: ^11.13.0 => 11.13.0
    @mui/icons-material: ^6.1.3 => 6.1.3
    @mui/lab: 6.0.0-beta.11 => 6.0.0-beta.11
    @mui/material: ^6.1.3 => 6.1.3
    @mui/material-nextjs: ^6.1.3 => 6.1.3
    @toolpad/core: 0.7.0 => 0.7.0
    @types/react: ^18.3.11 => 18.3.11
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript: ^5.6.3 => 5.6.3

Search keywords: vercel deployment

BCFCODE commented 3 weeks ago

Solved... It was all bout setting environmental variables!

github-actions[bot] commented 3 weeks ago

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue. Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

[!NOTE] @BCFCODE How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

mui / toolpad