Ah sry, think mixed it up. You have some problems with your images at all. As far as I know, Images are still not working within bolt if they are not SVGs (they work at least in my project).
Check below - works well in Bolt.new but once downloading project vfrom Bolt.new then uploading folder to Bolt.diy, it looses some functionality. I accept that but I think we can find a way of ‘refactoring’ a project so certain resources and authorizations can be resynced. If that makes sense as I’m sure this is a real thing.
See below as it works well but I’m getting several issues with Bolt.diy that don’t exist with Bolt.new. And, yes I really want to find a way to help you guys over here to improve your project - all this stuff is hard to deal with I know and you’re having a hard time but that’s where amazing things happen when you dig deep…
One question I have is once I receive an error like this below, I have to reload the browser as it seems to be a persistent issue and will continue to reoccur.
Edit: This depends on the Provider and/or the Model you are using. So you need to figure out if there is another good model/provider with higher rate limits.
You cant compare it like this, because you are not using the same Model/Provider as bolt.new does.
If you want to compare, you have to at least Claude 3.5 Sonnet (old) as Model, what is quite expensive in my view, but otherwise you cant compare
Please help me understand the difference between the two. I really want to start using Bolt.diy and happy to spend money using the product but I don’t see anything worth my time as yet. Seems there’s too much needing fixing right now.
A few things. I think you are getting a combination of CORS and mixed-content (mixing http and https content) errors as the images are likely from the web, and not in the project itself (neither Bolt.diy/Bolt.new generally bring in their own images). As for Qwen2.5 Coder 32B (open source/free model) being good, it is for simple things as long as you guide it, but it’s not going to one-shot things like Sonnet (commercial/pricy). Heck o1 doesn’t even seem to be as good!
For one, you are running locally, not behind HTTPS… this will cause all sorts of issues when trying to access web resources. Maybe try my tutorial on Deploying Bolt.diy with Cloudflare Pages (the easy way!). This would fix the HTTPS and mixed-content issues, but I’m not sure about the CORS problem. You could also always modify the code to load the images from the project (but you’d have to put them in it).
If you need better debugging, there is an option in the Bolt.diy settings, but I’m not sure it would have helped much in this case.
And while saying “there’s too much needing fixing right now” is fine, but part of it is understanding the thing you are using (differences and limitations), and not assuming it’s a bug. It’s not. But it is what it is.
Good luck!
P.S. Also @shawn, if you don’t mind a little experimentation, maybe try Qwen2.5 72B Instruct and Llama3.3 through HuggingFace for free. Or Google Gemini exp-1206 through Google Studio for free. You can also get 4o for free through GitHub, but Bolt.diy support is kind of pending.