Replies: 3 comments 1 reply
-
First thing I notice is your .env variables should all be strings. In other words:
or:
Not sure if that will fix your problem but its the only thing I can see wrong and might be why you're getting an "Invalid URL" error. |
Beta Was this translation helpful? Give feedback.
-
I'm facing a similar issue. It builds fine locally but fails on Github Actions.
|
Beta Was this translation helpful? Give feedback.
-
This happen to on v5 at Vercel TypeError [ERR_INVALID_URL]: Invalid URL
--
22:44:35.652 | at new NodeError (node:internal/errors:405:5)
22:44:35.660 | at new URL (node:internal/url:637:13)
22:44:35.660 | at 78021 (/vercel/path0/.next/server/app/_not-found.js:1:8158)
22:44:35.660 | at Function.t (/vercel/path0/.next/server/webpack-runtime.js:1:127)
22:44:35.661 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
22:44:35.661 | at async collectGenerateParams (/vercel/path0/node_modules/next/dist/build/utils.js:884:17)
22:44:35.661 | at async /vercel/path0/node_modules/next/dist/build/utils.js:1100:17
22:44:35.664 | at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/trace/trace.js:147:20) {
22:44:35.664 | input: 'moeg-mcs.vercel.app',
22:44:35.664 | code: 'ERR_INVALID_URL' |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Question 💬
I have this in my logs (localhost):
How to reproduce ☕️
I have this in my .env.local:
My next.config.js does not have any env vars
This is my route.ts file (app router):
Contributing 🙌🏽
Yes, I am willing to help answer this question in a PR
Beta Was this translation helpful? Give feedback.
All reactions