3 ms·

Bun does the same.

• bilalq 2y ago
  Sure, but switching from node to bun is a much more invasive change than switching from npm to pnpm. And not always possible.
  • spiffytech 2y ago
    Yes. I was more pointing out that blocking postinstall scripts is becoming a trend across multiple projects. Possibly a portent for the ecosystem as a whole. I could have communicated that more clearly.
  • croshan 2y ago
    It's quite easy, actually. We did this at work, recently. Bun is two things. Most commonly, it's known for its Node-competitor runtime, which is of course a very invasive change. But it can also be used purely as a package manager, with Node as your runtime: https://bun.sh/docs/cli/install https://bun.sh/docs/cli/install As a package manager, it's much more efficient, and I would recommend switching over. Haven't used pnpm, though--we came from yarn (v2, and I've used v1 in past). We still use Node for our runtime, but package install time has dropped significantly. This is especially felt when switching branches on dev machines where one package in the workspace has changed, causing yarn to retry all packages (even though yarn.lock exists), where bun only downloads the new package.