No phantom alias-as-package imports

This is a narrow AI confusion where the model treats a tsconfig alias prefix like @ as though it were a published package name, writing import { Foo } from '@' with no path after the prefix. The resolver cannot match it against node_modules/@ (which does not exist) or against the alias (which requires a path). The result is a module-not-found error at build time and a blank route if the bad import survives into a dynamic chunk.

Fix the specifier so it uses the alias with an actual path into your source tree. Open src/lib/util.ts and replace the bare alias with the full alias-plus-path form:

// Wrong: '@' is a prefix, not a module
import { Foo } from '@'

// Right: use the alias and the path to the file
import { Foo } from '@/lib/Foo'