Kage crawls any website and compiles the crawl into a single @golang binary — HTML, CSS, JS, fonts, the whole tree baked into one executable via embed.FS. 214 on HN. The novelty isn't the crawler or the asset rewriting (both 2015 tech). It's that the output is an executable, not a folder of HTML you have to host. Double-click, visit localhost, done. No installer, no static server, no node_modules. The use cases that surfaced in the thread weren't archival nostalgia — they were docs versioning, air-gapped enterprise, compliance snapshots, and conference handouts. WARC is still correct for 50-year horizons. For 'works next Tuesday on a laptop without WiFi,' this is the right shape. #OpenSource #devtools

Too many people asking Claude code to run “npm test” or “rm -rf node_modules” instead of just doing it in the terminal.

Just remove node_modules from .gitignore

ふむ、ここを local repository にしないと既存フォルダを使ってくれないのね デフォルトの New worktree のままだとホーム下に別フォルダとして複製されて .env とか node_modules とか全部置き直しになるので回避

Because people like to fuckaround. Users like to be retarded and find "bugs" that weren't supposed to be found. The board wants "moar revenue" - means "moar new features" The hackers like to poke holes and steal shit. The developers tend to skip tests "it's fine, lulz" Because vendors and 126,339 node_modules packages have to be upgraded, because see one above because they operating system had holes and now needs to be patched and patch broke obscure library #363 in those dependencies in them node_modules because see 2 above because CFO said, AWS is too expensive for spaghetti code devs wrote and their moving to Big Butt's Cloud & Lube datacenters in southern Kentucky now users say, "shits slow - we bounce" = sad board! Then government passes data compliance law requiring encryption of password and entire codebase needs to be refactored. And there is that one senior engineer nobody questions wakes up from his ayahuasca trip and declares, "I'm going to rewrite this entire legacy code in Rust" People love to fuckaround

cargo build giving one binary with zero deps is exactly why we chose rust for openclabs. no runtime, no node_modules, just a single binary. the overhead savings alone paid off in the first week

买 Mac 最后悔的一件事： 不是内存买小了。 是硬盘只买了 512G。 Docker、Node_modules、各种 AI 工具缓存、虚拟机…… 空间莫名其妙就没了。 现在外挂 1TB SSD 续命。 下次买 Mac，1TB 是底线。

7. Public APIs — 1,400 free APIs. Bookmark it. github.com/public-apis/publi… 8. .gitignore templates — never commit node_modules. github.com/github/gitignore 9. GitHub Pages — free hosting from your repo. pages.github.com Which one? 👇

du -sh node_modules is the most honest code review you'll run all week. You'll find the packages you chose — and dozens you didn't, pulled in by one 3-line helper. Reading "the code" stopped meaning your code a long time ago.

pnpm now. once you see how much disk npm wastes duplicating node_modules across every project you do not go back. the shared store and symlinks are the quiet win

rm -rf node_modules pnpm install

💡Quickly delete all node_modules from your system to free up space💡 When we do npm install or yarn install a node_modules folder is created which takes a lot of space and we never bother about deleting those folders. We can always regenerate those folders so it's good to delete those which are not needed. 𝗝𝘂𝘀𝘁 𝗲𝘅𝗲𝗰𝘂𝘁𝗲 𝘁𝗵𝗲 𝗳𝗼𝗹𝗹𝗼𝘄𝗶𝗻𝗴 𝗰𝗼𝗺𝗺𝗮𝗻𝗱 𝗶𝗻 𝘁𝗵𝗲 𝘁𝗲𝗿𝗺𝗶𝗻𝗮𝗹 𝗳𝗿𝗼𝗺 𝗶𝗻𝘀𝗶𝗱𝗲 𝘁𝗵𝗲 𝗳𝗼𝗹𝗱𝗲𝗿 𝘄𝗵𝗲𝗿𝗲 𝗮𝗹𝗹 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗮𝗿𝗲 𝘀𝘁𝗼𝗿𝗲𝗱. npx npkill It will list out all the node_modules folders from the current folder and its subfolders. Then you can navigate through the list by pressing up and down arrow keys and just press spacebar to delete a particular node_modules folder. Manually deleting the node_modules folder takes a lot of time. But using npkill is very fast. You just hit the spacebar and the folder is instantly deleted. If you don't want to use the npx command, you can install the npkill npm package globally using npm install -g npkill and then just run npkill command from the terminal. Just give it a try. You will love it. It's a great way to free up your disk space 🙂 I have freed up more than 10 GB of space using it. 𝗙𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝘂𝘀𝗲𝗳𝘂𝗹 𝗰𝗼𝗻𝘁𝗲𝗻𝘁, 𝗱𝗼𝗻'𝘁 𝗳𝗼𝗿𝗴𝗲𝘁 𝘁𝗼 𝗳𝗼𝗹𝗹𝗼𝘄 𝗺𝗲. #javascript #reactjs #nextjs #webdevelopment

512G 做开发真的很快就开始焦虑，尤其现在一堆模型、缓存、node_modules、素材文件混在一起。内存和硬盘这种东西，买的时候心疼，后面会感谢自己。

pnpm for me, the disk savings and the strict node_modules alone make it worth it. bun is slowly creeping in for scripts and quick stuff though

If your Docker image for a Node.js or React app is over 1GB, you are doing it wrong. 🐳📉 Stop shipping your `node_modules` and source code to production. Use Multi-Stage builds: Stage 1: Install dependencies and compile the build.

X上的AI大神们，有一个棘手的问题。Windows 下面delete这个node_modules太慢了，有什么trick吗？试了robocopy and rimraf, 都不怎么好用。

Developers destroying their team's Git: ❌ Committing directly to main ❌ "fixed stuff" commit messages ❌ Force pushing shared branches ❌ 1 commit, 47 file changes ❌ Pushing node_modules 💀 Clean Git devs do this instead ↓↓↓