Issue summary -
The issue happened in a macOS environment after creating a new jsx file via vscode. Initially, the created file included lines that caused an error. After removing the lines causing the error, vite kept accessing a file containing the stale erroneous content.
After recreating the file, copying the jsx file’s content to the new file, and restarting vite, the issue disappeared. We think that the root cause was that the file had the “Stationary pad” file attribute.