And it would be nice if you could.
I’ve worked extensively with replit over the past couple of months and it’s good for prototypes and low risk MVPs. But for it to be used by software engineers, it needs to start with
- Testability: I’ve wasted so much time because as the project got larger or more complex, things started breaking. This is normal. What is not normal is no access to simple ways of doing isolated testing with unit functional and integration tests.
- Maintainability: the code that’s generated is the average of all the code on the internet. It’s sometimes great. Often it’s horrifyingly bad. It also cheerily duplicates datastructures and methods all over the place, making for much confusion down the line.
- Performance: no intelligence at all with database access that I experienced. Add a new access pattern, not a flicker of reflection on how indexes need to be updated to support it.
Anyway I’ll still (try) to deploy to replit from a local build of my thing, but last time I tried that it was a bit of a nightmare too so I might end up having to find another host as well.
Thanks, and good luck team 
PS for crissake fix the maddening Agent vs Assistant double chatbot thing. It is broken, and is the source of, in my estimates, 50% of the 1 star reviews on Trustpilot.