eval("require")(PACKAGE) fails on Vercel in Pages router, unless pre-rendering. #63492
Comments
|
@samijaber can you detail what's the expected breakage? |
|
Closing this issue as I found a workaround.
import { Head, Html, Main, NextScript } from "next/document";
// import that isn't technically used
import ivm from "isolated-vm";
export default function Document() {
return (
<Html lang="en">
<Head />
<body>
<Main />
<NextScript />
</body>
</Html>
);
} |
|
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Link to the code that reproduces this issue
https://github.com/samijaber/nextjs-monorepo/
To Reproduce
see https://vercel.com/sami/nextjs-monorepo-nextjs-pages for example of deploy
Current vs. Expected behavior
I expect app to deploy successfully, but it does not
Provide environment information
N/A (this is a Vercel env issue, not a local issue)Which area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed)
Additional context
My linked repo includes a pages router and an app router example.
Things to note:
https://github.com/samijaber/nextjs-monorepo/blob/35c7421fefb2f453f682717dca291b791629dd36/nextjs-pages/src/pages/%5B%5B...page%5D%5D.tsx#L5
Removing this
getServerSidePropswill make the app successfully run on Vercel.The text was updated successfully, but these errors were encountered: