whenever there’s another #npm #supplychain attack, it’s time to start victim-blaming. unironically. don’t use npm, use #pnpm (or #bun).
pnpm stores your packages in a single central repository instead of downloading them all every time, and it also doesn’t run build scripts by default unless you ask it to. plus, it’s faster, but that’s less important.
if you use plain npm, you’re not a victim, you’re a perpetrator.
[ERR_PNPM_IGNORED_BUILDS] Ignored build scripts: @parcel/[email protected], [email protected], [email protected], [email protected]
Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.Ruby, Java, TypeScript 비교: Claude Cowork DOCX 플러그인 개발기
DOCX 파일(Zip+XML) 처리를 위해 Ruby, Java, TypeScript 세 가지 언어로 플러그인을 순차적으로 구현하며 각 언어의 라이브러리 안정성과 개발 효율을 비교함
🔥Hono × 🥟Bun × 🔼Next.jsでWebアプリ開発ハンズオン
https://qiita.com/tomo-ryo/items/3e0529f689bcb39ede97?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Bun's problem may be developing in the open
My Thoughts on Bun's Rust Rewrite
Bun의 JavaScript 런타임이 Zig에서 Rust로 AI(Claude) 자동 생성 코드 기반으로 6,755 커밋, 6일 만에 전면 재작성되었다. Zig는 초기 빠른 프로토타이핑과 고성능 구현에 핵심 역할을 했으나, 수동 메모리 관리의 인지 비용이 빠른 개발 문화와 맞지 않아 Rust로 전환했다. 그러나 AI가 작성한 코드가 인간 리뷰 없이 바로 프로덕션에 투입된 점은 장기 유지보수와 예측 불가능한 버그 대응에 큰 위험 요소로 지적된다. 이 사례는 AI 자동 코드 생성의 실무 적용과 신뢰성 문제를 시사한다.
Before we discuss Rewrite Bun in Rust, there's something that needs to be said, because no one is saying it. Bun stands where it does today because of Zig. Jarred chose Zig back then not because it was "cool," but because Zig enabled a small team to rapidly prototype a high-performance JS runtime without a GC, without a heavy runtime. Zig's low friction, direct memory manipulation, and straightforward C interop were the core reasons Bun could punch above its weight on performance with an extremely small team in its early days. The architecture, data structures, and low-level design of Bun that you see today – that was shaped by Zig.