⌘K
Vizkiel Come on, man. I’ve already got a million things going on with the website, and I was seriously considering buying domains for several of my sites because I thought Vercel was actually gonna be useful. And then I find out you guys disabled manual code editing? Like, seriously, who thought that was a good idea? Whoever came up with that decision deserves a fuc*ing promotion… somewhere else. Because there’s no way this was the best idea anyone in the room had.
Colwalkurtz 7852 I believe your decision to remove direct code editing in v0 is extremely short-sighted and blatantly profit-driven. To update simple details on a page, I now have to go through the chat and consume credits, unless I rely on external tools like GitHub or VS Code. This does not keep users within v0; it pushes them to become independent of it. What was the rationale behind this? Until now, I used v0 with great satisfaction and willingly spent a significant amount because the service was excellent. Forcing me out of the v0 environment makes my workflow far more cumbersome, which will only lead to frustration and drive me away. At that point, using GitHub alongside any other AI tool, I can easily make changes on my own. In the end, I believe this change will decrease your revenue rather than increase it. Please reconsider this step and let us work inside v0 as we did before. Thank you for your time and attention.
Greguarr v0 Vercel without code/files/folder edit - It's a huge downgrade for this tool - which, up to now, has been getting better and better. I hope this is just a temporary flare-up stemming from some licensing issues regarding the use of VS Code.
Amy Egan Thanks for reporting this. I'm checking with the team about it
Romlenzotti Hi @amyegan Thanks for your message. On the example I finally fixed the problem. ```json { "$schema": "https://openapi.vercel.sh/vercel.json", "bunVersion": "1.4.x", "framework": "bun" // this line is required, but missing in the example } ``` But in the vercel backoffice Bun framework is missing. This is why I haven't tried that, and in my mind bunVersion should trigger bun automatically. After that I faced to another issue. One the dependencies (universal-github-app-jwt) of octokit to consume github API use internal imports to resolve crypto lib depending on the : ```json { "imports": { "#crypto": { "node": "./lib/crypto-node.js", "default": "./lib/crypto-native.js" } }, ``` import { subtle, convertPrivateKey } from "#crypto"; // >> unable to resolve #crypto But in your Bun integration, theses imports aren't resolved. Use a bun patch doesn't solve this problem. At this step, I decided to back forward to a Node.js stack which is more stable ;) (I assume the Bun support in vercel still in beta). Let me know if you need more details on the different issues. See you
Amy Egan Glad you got it working! I'll add these notes to the internal ticket for the team
