Packages that use pinst are broken when they are installed with npm 10.4.0 and later about pinst HOT 5 CLOSED

Thanks for letting me know! I hope it'll get resolved soon.

from pinst.

It should have a low impact as pinst is useful for yarn in particular

from pinst.

Unfortunately the problem occurs at package installation time, so it affects packages built with yarn if the end user installs them with npm.

Some of my packages use yarn and pinst, and if you install those packages as a dependency in another project with npm 10.4.0+, then npm will try to run the _postinstall script, and either fail or do something stupid.

from pinst.

You're right, didn't see things from this point

from pinst.

Hi @typicode. The above description of this problem is not accurate, but there is a problem you ought to know about.

I've emailed you privately about this for reasons that will become apparent when you read the email. Please be on the lookout for an email from [email protected].

Closing this issue for now.

from pinst.