One new error is v0 attempting to run typescript but now says it can only do SQL, Python and Node.js scripts. I’ve spent 40 minutes trying to make database changes but got this error twice this morning. I had to delete all of these adjustments because v0 couldn’t run the script.
The script runner doesn’t support typescript yet, if you ask it to convert them to JS files it should start working
I’ve pinged the v0 team, TS support here is definitely possible just not implemented yet
I’ve had this typescript error at least four times this week. It is creating new problems in my app. Very irritating if it doesn’t work yet.
Fifth time it is trying to run typescript. I think it has corrupted some of my files because of this internal confusion. I’ve been trying to diagnose my database errors because of these script errors all day, today.
These new typescript errors have created serious problems with my app connecting to its Supabase database. A lot of internal functions broke because it attempted to use typescript than convert to SQL, Python or Node.js.
The problem is with every conversion prompt, v0 adds new phantom requests because of the agent function. I’ve lost a day and half of progress plus $24 in credits. Not cool.
Past ten days on v0 has felt like one step forward, two steps back. Very painful experience right now.
the Free Fix with v0 had 3 debugging errors this morning and stopped working. it stopped thinking three times after working on the app all morning. refreshing helped but it stopped midday several times.
I’m getting new script errors. This time it is related to my SQL database. For some reason, I need run to +80 scripts all over again after forking the project. The problem is it has created new script errors and this configuration to run files doesn’t go away now.
I’m getting a new SQL script problem. Previously I could run SQL scripts from the chatbox but now it is asking me to run the query from Supabase. Not a serious problem but this is a new additional step that didn’t exist before. Not sure why it was added.
I’m not understanding the logic of this new scripting process.
Before I could run SQL, Node.js and python scripts from within the v0 chatbot. But now I need to copy the SQL script and run the query from Supabase to connect tables. It has added extra steps. I had two SQL script errors and the Supabase assistant can’t solve script errors as well as v0.
The additional back and forth is creating too much breakage, and consuming unnecessary credits.
