Zoltan Kochan

Zoltan Kochan

@kochan.io

Developer, maker of @pnpm.io Works on dependency management at bit.dev

2.1K followers181 following159 posts

I have some early benchmark results with my custom @pnpm.io registry. In different scenarios, overall install times are 2 to 7 times faster than even the already very fast pnpm in Rust. Looks promising.

Zoltan Kochan reposted

Therein lies the rub: AI cannot have “ideas” of its own. Every “idea” you thought AI had came from a person, either through prompting or theft. The way to jumpstart the “idea machine” is to have people focused less on survival and more on living passionately.

Vox@vox.com

America, you have spoken loud and clear: You do not like AI. But what if AI is the way to restart the world’s idea machine?

Zoltan Kochan reposted

🚀 pnpm v10.21 is out! This release introduces two powerful new security & compatibility features: 1️⃣ Automatic Node.js runtime installation for dependencies 2️⃣ Configurable trust policy for detecting supply-chain downgrades 🧵👇

Zoltan Kochan reposted

Zoltan Kochan reposted

After recent npm supply chain attacks, @pnpm.io 10.16 adds a setting for delayed dependency updates. Tools like Taze and npm-check-updates are testing similar “maturity” options, hinting at a cautious new trend in #JavaScript package management. socket.dev/blog/pnpm-10... #NodeJS

socket.devpnpm 10.16 Adds New Setting for Delayed Dependency Updates -...pnpm's new minimumReleaseAge setting delays package updates to prevent supply chain attacks, with other tools like Taze and NCU following suit.

With the changes to the lockfile format and the new types of fetchers that were added to pnpm, now it is really easy to make pnpm an installer for anything bsky.app/profile/pnpm...

pnpm@pnpm.io

pnpm v10.14 is shipped with support for runtime engine installation. Node, Deno, and Bun are supported. pnpm.io/blog/release...

I am thinking about a better name for the pnpm "virtual store". Which is where the dependency is written with its unique dependency graph. I couldn't find any prior art to this. Maybe "Package Context" could work. Or "fully resolved package store" but that's long.

Many packages request funding by printing message with postinstall scripts. What if instead of requesting funding we would promote sponsors? After all, we want companies to sponsor open source projects as they are the ones that make profit from it.

A lot of packages use postinstall scripts for printing out messages about funding. Could there be a better way to do this? pnpm doesn't even print the outputs from these scripts.

Zoltan Kochan reposted

Ton of npm libs use github.com/cosmiconfig/... to load their config files. But, today I learned, if nodejs dies, the temporarily file created by cosmiconfig remains 🤷‍♂️ I fixed this locally in 5 mins thanks to the amazing patch ability of @pnpm.io (kudos @kochan.io!) and the LLMs era of code editors

github.comGitHub - cosmiconfig/cosmiconfig: Find and load configuration from a package.json property, rc file, TypeScript module, and more!Find and load configuration from a package.json property, rc file, TypeScript module, and more! - cosmiconfig/cosmiconfig

I am wondering if we should always use some custom protocols like "kahuna:" when the registry is not the public npm registry. So package.json would get something like this:

Zoltan Kochan reposted

pnpm v10.9 is out with native support for the JSR registry! You can now install packages from JSR using the "jsr:" protocol. For example: pnpm add jsr:@hono/hono

I've seen Steven Seagal movies and I've seen "Snow White". I don't think that's fair. Whatever you think about "Snow White", it isn't worse than the latest Steven Seagal movies.

It would be nice if an LLM could help with writing "changesets" and detecting which of the changes are breaking and which are backward compatible. Currently I use exact versions to reference any packages from the same workspace as it is so hard to avoid mistakes.