This team repo has no index.html in its publish directory ., so there is nothing to serve.
The build command failed. Fix the errors below and push to main again — the site rebuilds automatically.
npm error code EUSAGE npm error npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing. npm error npm error Invalid: lock file's picomatch@2.3.2 does not satisfy picomatch@4.0.5 npm error Missing: picomatch@2.3.2 from lock file npm error npm error Clean install a project npm error npm error Usage: npm error npm ci npm error npm error Options: npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling] npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]] npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]] npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit] npm error [--no-bin-links] [--no-fund] [--dry-run] npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]] npm error [-ws|--workspaces] [--include-workspace-root] [--install-links] npm error npm error aliases: clean-install, ic, install-clean, isntall-clean npm error npm error Run "npm help ci" for more info npm notice npm notice New major version of npm available! 10.8.2 -> 12.0.1 npm notice Changelog: https://github.com/npm/cli/releases/tag/v12.0.1 npm notice To update run: npm install -g npm@12.0.1 npm notice npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-07-11T10_57_36_293Z-debug-0.log added 362 packages, and audited 363 packages in 11s 146 packages are looking for funding run `npm fund` for details 2 moderate severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. > undercut@0.1.0 build > next build ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.2.10 (Turbopack) Creating an optimized production build ... ✓ Compiled successfully in 2.8s Running TypeScript ... Finished TypeScript in 2.2s ... Collecting page data using 3 workers ... Generating static pages using 3 workers (0/4) ... Generating static pages using 3 workers (1/4) Generating static pages using 3 workers (2/4) Generating static pages using 3 workers (3/4) ✓ Generating static pages using 3 workers (4/4) in 204ms Finalizing page optimization ... Route (app) ┌ ○ / └ ○ /_not-found ○ (Static) prerendered as static content ::notice::npm run build успешен
HackOnVibe CI — this page auto-replaces a broken deploy so you can see exactly what went wrong.