Hmm, why does it happened to me? all files I totaled size only 1MB or more, but, why?
1 Like
large files, junk files. Check for those
Or try enable-pnpm to re-install all your modules once again to make sure.
i tried to remix this project(just for test), but why is different 
my new remixed project has 80MB disk usage and my old project 151MB(pict).
hmmm, maybe there is a glitch somewhere, can you run ls and send a screenshot?
1 Like
the terminal, open the terminal and run:
ls
then send a screenshot
Looks good to me. Does enable-pnpm help?
try deleting node_modules and running npm install
rm -rf node_modules
npm install
1 Like
idont know 
still same, node module already deleted
Use rm -rf /app/.git/ to delete the rewind cache to save a lot of disk space.
@SplitXPlayZ that is never a good idea.
It will delete any records of rewinds and the user won’t be able to rewind. This might seem like a good solution to some but truthfully it is a bad idea
I used it, and it will delete the rewind cache but it will save disk space.
EDT: Forgot to add warning. (do NOT try this at home or anywhere).
My methods are listed there:
- Type
git gcorgit prunein your terminal to remove useless folders/files from your project. - Remove useless packages from your
package.json. - Type
rm -rf /app/.git/in your terminal to remove your rewind cache. (Not recommended anyway)
Do NOT remove/delete your rewind cache, if you doesn’t know what you are doing.
1 Like
Thanks for the warning, through.
wow thats weird. I have lots of projects, but i don’t have that 
No problem
Your cache is full, likely the ffmpeg cache folder specifically.
Here is what you need to do: the commands are in bold text
YourRoot:~
$ cd ./.cache/ffmpeg-static-nodejs
YourRoot:~/.cache/ffmpeg-static-nodejs
$ du -l
186064 .
YourRoot:~/.cache/ffmpeg-static-nodejs
$ rm “*” ← Asterisk for all files…
YourRoot:~/.cache/ffmpeg-static-nodejs
$ du
30 .
As you can see it was the ffmpeg cache file that was hogging the disk space in the above example after doing a du -lh command in YourRoot directory.
CD to the relevant directory and delete the cache file… that should solve the issue and you can confirm by doing another du after you delete it and you will see the fruits of your labour.