-
I am receiving this error when building my Next.js website using
It is occurring both on my Windows WSL machine and on Vercel's servers. Is there any reason why? I don't have an import anywhere in my code that imports "URL" or "url". By the way, my source code is publicly available on GitHub. Thank you in advance. @mdx-js/mdx version: 2.0.0-rc.2 node.js version: 16.13.1 /** @type {import('next').NextConfig} */
module.exports = {
reactStrictMode: true,
}; tsconfig.json: {
"compilerOptions": {
"target": "es5",
"lib": ["dom", "dom.iterable", "esnext"],
"allowJs": true,
"skipLibCheck": true,
"strict": true,
"forceConsistentCasingInFileNames": true,
"noEmit": true,
"esModuleInterop": true,
"module": "esnext",
"moduleResolution": "node",
"resolveJsonModule": true,
"isolatedModules": true,
"jsx": "preserve"
},
"include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
"exclude": ["node_modules"]
} |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Fixed in Next.js 12This issue apparently has been fixed after upgrading to Next.js 12. However, I highly doubt that this issue is because of Next.js 11, try re-installing your packages ( Sorry for any inconvenience caused 😅 |
Beta Was this translation helpful? Give feedback.
Fixed in Next.js 12
This issue apparently has been fixed after upgrading to Next.js 12. However, I highly doubt that this issue is because of Next.js 11, try re-installing your packages (
rm -r node_modules && yarn install
). If it still doesn't work, then try upgrading to Next.js 12.Sorry for any inconvenience caused 😅