Code Editor freezes on syntax errors + auto-save behavior changed

The editor's handling of syntax errors has become a serious usability problem.

Right now, if there is any temporary syntax issue while editing (for example, a method or style block is still incomplete), the editor detects the syntax error and then completely freezes, making further editing impossible.

This breaks the most basic editing workflow. In many cases, I'm forced to revert the changes, finish editing in another editor, and then paste the code back into v0.

change-mode

There's also another issue with auto-save behavior.

Previously, manual edits could remain unsaved until I confirmed them. Now, although the save indicator briefly appears in the bottom-right corner, it disappears immediately and the editor auto-saves everything automatically.

Combined with the current editor instability, this behavior is risky and frustrating.

Please investigate both:

The editor freezing when syntax errors exist during editing
The aggressive auto-save behavior replacing the previous manual save flow

These issues are heavily impacting day-to-day development experience.

Leaderboard Winner

Hi Raymond,

I can reproduce the syntax-error part in a basic v0 project.

In app/page.tsx, if I temporarily leave JSX incomplete while editing, the editor becomes difficult/impossible to continue editing until the syntax is fixed or reverted. That makes normal incremental editing risky, because incomplete JSX is common while typing.

A useful minimal repro seems to be:

Open a v0 project.
Edit app/page.tsx.
Start editing a JSX line and leave it temporarily incomplete.
Try to continue typing before the syntax is valid again.
The editor can freeze or stop accepting normal edits.

This feels like the editor/linter/parser is reacting too aggressively to transient syntax errors. Ideally, temporary syntax errors should be shown inline, but the editor should still remain editable.

I also agree that the auto-save behavior should be clarified. If manual edits now save automatically, the UI should make that very explicit because it changes the expected safety of editing directly in v0.

Please fix this problem ASAP, I'm really fed up with it lately