What happens when postinstall is no longer supported?

[ajvincent]

https://www.theregister.com/devops/2026/06/10/github-pulls-pin-on-npms-auto-run-scripts/5253453

I'm not trying to be a troll... I'm genuinely curious, because I've used patch-package in the past. But if this package depends on postinstall, and postinstall stops working in npm 12 a month from now, users will have to do this manually.

It's quite possible I'm misreading this, since they do talk about --allow-scripts. But still.

[oserrabassa-jcm]

We recently updated to NPM 12 and patch-package stopped executing due to the new postinstall restrictions. We ended up creating a new package.json script "patch": "patch-package" which basically gets executed after any npm install. You could even create a script that does both in one go like "install-patch": "npm install && patch-package". Not sure if there are better solutions than these.

[ShGKme]

postinstalls are not removed, they just need to be explicitly allowed (approved).

[manzoorwanijk]

We recently updated to NPM 12 and patch-package stopped executing due to the new postinstall restrictions. We ended up creating a new package.json script "patch": "patch-package" which basically gets executed after any npm install. You could even create a script that does both in one go like "install-patch": "npm install && patch-package". Not sure if there are better solutions than these.

I added native patching in npm v12. You no longer need a third-party solution on v12.

[orta]

Very cool 👍🏻