Problems deploying Next.js problem, cryptic error
Anonymous
PROOP

17 days ago

I'm having the following problem to deploy a Next.js app. The biggest problem is that there is no really an error.

npm warn config production Use --omit=dev instead.

> frontend@0.1.0 build

> next build

▲ Next.js 16.1.1 (Turbopack)

Creating an optimized production build ...

> Build error occurred

VzL21vZHVsZS1ub3QtZm91bmQKCgouL3NyYy9jb21wb25lbnRzL3VpL2...

Attachments

logs.177136...
logs.177136...
$10 Bounty

3 Replies

Railway
BOT

17 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway • 17 days ago

dharmateja
HOBBYTop 1% Contributor

17 days ago

did you commit these src/lib/utils and/or src/lib/auth files?

Anonymous
PROOP

17 days ago

Everything has been committed and I'm using relative paths. How do you see the "src/lib/utils" files? I don't find that in the error message

ruvalcaba18
FREE

16 days ago

Hey wave emoji

Based on the build log, the errors are coming from these files:

  • src/components/ui/input.tsx

  • src/components/ui/label.tsx

  • src/components/ui/separator.tsx

  • src/components/ui/table.tsx

  • src/app/page.tsx

  • src/components/AppHeader.tsx

All of them are importing from lib/utils or lib/auth, so I would start by checking those imports carefully.

Make sure:

  • utils and auth are correctly imported in each of those files.

  • The relative path (../ or ../../) is correct based on the file location.

  • The file names match exactly, including lowercase/uppercase (Linux is case-sensitive, so Utils.ts is different from utils.ts).

I’d review those files one by one and confirm the imports match the actual folder structure exactly. That should point you in the right direction +1 emoji

Status changed to Open brody • 16 days ago

Loading...