bug(ui): next.config.js contains invalid JavaScript (stray code fence)

[purvanshjoshi]

Severity

Low

Impact

next dev, next build, and next start all fail to load the Next.js configuration with a SyntaxError, blocking every UI command. This is currently masked because the UI has no pages to serve anyway, but it must be fixed before any UI work resumes, and CI's || true (ci.yml line 98) silently swallows the failure.

Description

packages/ui/next.config.js is not valid JavaScript. A stray Markdown code-fence character (``` ```) appears on the final line, pasted into the file alongside the actual module contents:

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
}
module.exports = nextConfig
` ` `   // <-- stray code fence, invalid JS

Node.js throws when Next.js requires this file, so all Next.js CLI commands abort before the app even starts.

Sub-Issues

• Sub-Issue 4.1: Remove the stray code fence
  Delete the trailing ``` line so the file is a plain, valid CommonJS module.
• Sub-Issue 4.2: Make CI fail on UI build errors
  Remove the || true in the UI build step (ci.yml line 98) and/or add a config-smoke step (node -e "require('./next.config.js')"), so syntax and build regressions in the UI are caught.