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

Vercel deployment errors #4274

Closed
BCFCODE opened this issue Oct 17, 2024 · 2 comments
Closed

Vercel deployment errors #4274

BCFCODE opened this issue Oct 17, 2024 · 2 comments

Comments

@BCFCODE
Copy link

BCFCODE commented Oct 17, 2024

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 BCFCODE added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Oct 17, 2024
@BCFCODE
Copy link
Author

BCFCODE commented Oct 17, 2024

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

@BCFCODE BCFCODE closed this as completed Oct 17, 2024
@github-actions github-actions bot removed the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Oct 17, 2024
Copy link

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.

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

No branches or pull requests

1 participant