Your latest push did not put a working site online yet. Here is exactly how our system decides to build your site — and how you control it by your files.
build script in package.json (or no package.json), we put your files online exactly as they are, so your index.html shows up.package.json has a build script for a static tool (React/Vite/Astro, or Next.js with output:'export'), we run the build and publish the built folder (dist/build/out).build but no output:'export', it needs a live server, so we run it for you in a container (you may need to give us the API keys it needs).Right now your repo is in: 🔵 Server app. To switch: delete the build script → 🟢 Plain website · add output:'export' → 🟡 Built app · keep it + send us the API keys → 🔵 Server app.
The build command failed — the exact error is below. Fix it (or switch build mode above), then push to main again — the site rebuilds automatically.
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@semantic-release/github@12.0.9',
npm warn EBADENGINE required: { node: '^22.14.0 || >= 24.10.0' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@semantic-release/npm@13.1.5',
npm warn EBADENGINE required: { node: '^22.14.0 || >= 24.10.0' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: 'semantic-release@25.0.6',
npm warn EBADENGINE required: { node: '^22.14.0 || >= 24.10.0' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
added 723 packages, and audited 867 packages in 15s
253 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
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
> dorahacks-hackonvibe-launchcopilot@1.0.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 3.3s
Running TypeScript ...
Finished TypeScript in 5.0s ...
Collecting page data using 3 workers ...
Generating static pages using 3 workers (0/6) ...
Generating static pages using 3 workers (1/6)
Generating static pages using 3 workers (2/6)
Generating static pages using 3 workers (4/6)
✓ Generating static pages using 3 workers (6/6) in 198ms
Finalizing page optimization ...
Route (app)
┌ ○ /
├ ○ /_not-found
├ ƒ /api/analyze
├ ƒ /api/extract
├ ƒ /api/kit
└ ○ /icon.svg
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand
::notice::npm run build успешенHackOnVibe CI — this page auto-replaces a broken deploy so you can see exactly what went wrong.