Show HN: My Next.js .next folders hit 34 GB, so I built next-nuke to clean them
1–5 of 5 posts
Re: Show HN: My Next.js .next folders hit 34 GB, so I built next-nuke to clean them
#2[deleted]
Re: Show HN: My Next.js .next folders hit 34 GB, so I built next-nuke to clean them
#3Does --full do anything to avoid clobbering an install that's mid-flight, or is
it assumed nothing else is touching node_modules?
Re: Show HN: My Next.js .next folders hit 34 GB, so I built next-nuke to clean them
#4[flagged]
Re: Show HN: My Next.js .next folders hit 34 GB, so I built next-nuke to clean them
#5Does --full do anything to avoid clobbering an install that's mid-flight, or is it assumed nothing else is touching node_modules?
No, it assumes nothing else is touching node_modules. No lock, no check for a running install; the only gate is the confirmation prompt, and --yes removes that.