I’ve been with Replit for 2 years and I have LOADS of Repls. Last I heard there was an account-wide storage limit for regular and Hacker plan users (Hacker being 5GB if I remember correctly) and I have reason to believe I am hitting this limit. Projects that I used to scaffold easily now cause -122 system errors because I’m exceeding the disk quota installing dependencies.
Not sure if this is some new change or just because I’m so old that I finally hit the limit, but its becoming a pain point when trying to build larger webapps like I used to a while ago .
I asked a Replit Engineer prior to this post and they said they weren’t at liberty to say whether account-wide limits are still in place - understandable. I would very much like a definitive answer and perhaps a better solution that the one I’m currently drafting.
My plan right now is to just write a script using a library I made (crosis4furrets) that will connect to Repls I own and run rm -rf node_modules (or similar depending on the packager) and remove the node_modules folder from all of my Repls, and the I go back and reinstall modules for Repls I do use. This would clear out wasteful space while still preserving my project’s codebase (and yes I will be open sourcing this tool for others to use of course ).
At the end of the day though it would be useful to either be given a guarantee as to what’s going on or clarify details on the account-level storage limit. While I can’t wait for Infinity Drive, I don’t want to pay extra if it’s just a matter of my account being old. I will keep this post updated on my little experiment clearing out my account though
Can you send me the link to one of your Repls that is encountering the out-of-storage error? Account-wide storage shouldn’t affect the Repl’s ability to run, that’s part of the per-Repl storage limitation.
can you send me a link to a repl where this happens as well? I’m curious A while ago I had disk quota errors which seemed to be because nix was creating compilation files which it had to do because of some bug in how swift was packaged, and those gobbled the last of the storage available on that partition