Something must be done about the publishing system

General
1

maybe a kind of pre-publish error seeker system that detectes all the publish errors at once. Right now it’s a real nightmare since the publish system detects errors one by one. In big project there might be tens of them which each error detecting and fixing takes about 5-10 minutes. We are talking here about hours of hours of works just on errors solving.

2

Have you tried to build a CI/CD pipeline using pre-commit hooks with formatting, linting, type checking and test frameworks to audit your code before building to production?

3

I’m not a coder and I’ve no idea what it is. But I do expect the platform to spare me this knowledge.

4

Ignorance is not a solution, it’s a vulnerability, where even a basic understanding can benefit you and the platform can implement it if you ask the right questions.

5

Ironically Claude fixed my broken Gemini code. Gemini is not up to date with the fast pace changes happening in firebase. Gemini also does not have full knowledge on Firebase DataConnect docs and causes lots of errors in the GraphQL files.

I’m days away from giving up on Firebase Studio

6

Thanks for the feedback and sorry for the frustrating experience. The issue you’re running into is Next.js apps are served differently in development and production environments. The Next.js development environment (used for the preview of your app in Firebase Studio) is designed for rapid iteration– offering features like hot reloading– and is more forgiving with compile rules. The production environment (used when you Publish your app) is optimized for stability, security, and performance, enforcing stricter compile rules. This distinction results in undetected compile errors surfacing when you Publish.

We understand that this is a painful debugging experience, and we’re actively working on improving it. In the meantime, you can check for errors before publishing by switching to Code mode, opening a Terminal, and running npm run build. If you get errors, copy and paste the error message into chat to fix them. Once npm run build succeeds, you should be good to Publish. Hope that helps!