Your private JavaScript registry can now publish to the public.
Public packages are now GA. Publish and install the packages you want to share with the ecosystem. Read the full announcement here ↓ vlt.io/blog/public-packages
🏛️ announcing hunk v0.22.0 - now w/ `hunk log`
- TUI for reviewing git/jj history
- quickly jump from commit → diff
- OR multi-select a commit range
- supports mouse + all colour themes
also in this release: multi-line comments, lower memory usage, faster --watch, & more! 🔈
This can't be overstated. Funny enough, dual support outpaces esm-only (expected, as maintainers want the broadest interop). We're almost a decade in & esm-only pkgs are only growing at ~2% /yr; at that pace, it'd take another decade to hit ~50%.
refs. github.com/wooorm/npm-esm-vs…
vlt 1.0.5 is here 🚀
Faster installs when package.json declares duplicated depedencies: up to 40% smaller.
Safer installation and package publishing by default: tar decompression caps & path-traversal hardening enforced. github.com/vltpkg/vltpkg/rel…
Crazyy...someone measured Claude's vocabulary across 47,464 GitHub pull requests.
A word cluster that didn't exist in 2025 is now 45% of human-authored PRs.
The top word is "load-bearing"
Works perfectly on page 1.
Page 1000 takes 30 seconds.
Page 10000 crashes the server.
Pagination is supposed to make it faster.
It's making it slower.
Why? 🤔
Damn.. @vltpkg is great 👌 Bye NPM SHIT!
Simple setup:
- VLT proxy CF Worker with 2 service tokens
== read-only token for consumer reads
== read-write for convenience
- have a Github CI that publish to VLT with OIDC.
- have npm .wgw .lol as registry for ONLY MINE pkgs
Lovely.
Cross-ecosystem package tracking is a nightmare when every tool formats dependencies differently. 🧵
Enter PURL (Package URL)—the open standard bringing sanity to software supply chains.
Add ?qualifiers for OS/arch details and #subpath for specific subfolders inside a package, and you have an unambiguous, deterministic identifier for any software artifact.