Don't run the pre/post scripts

[zkochan]

NOTE: It is possible to return how pre/post scripts worked by setting the enable-pre-post-scripts setting to true (since v6.1.0)

---

When running pnpm run foo, don't run the prefoo script and the postfoo script.

Yarn 2 already deprecated the pre/post scripts:

In particular, we intentionally don't support arbitrary pre and post hooks for user-defined scripts (such as prestart). This behavior, inherited from npm, caused scripts to be implicit rather than explicit, obfuscating the execution flow. It also led to surprising executions with yarn serve also running yarn preserve.

https://yarnpkg.com/advanced/lifecycle-scripts

[aminya]

Does this affect postinstall as well? Because many packages use postinstall to perform operations that are not covered by the package manager (such as copying fonts, building, etc). In my opinion, not running that is not a good approach!

[zkochan]

no, the standard lifecycle scripts like postinstall or prepublishOnly are not affected.

[zkochan]

but prepostinstall will not be executed. And postpostinstall as well.

[Djaler]

Is there are a way to enable it again? I think this is useful feature in some cases

[zkochan]

I don't see much value in it. You may just add "start": "pnpm prestart && node server.js" if you need it.

It is not some action that you do frequently. Mostly you just add a script once and never change it.

[Djaler]

Makes sense

[TigersWay]

I don't see much value in it. You may just add "start": "pnpm prestart && node server.js" if you need it.

It is not some action that you do frequently. Mostly you just add a script once and never change it.

May I disagree?
Nearly all my scripts have been written with these "pre" & "post" hooks to deal specifically with env variables or clean actions. And I know I am not the only one.
Just to be clear I honestly don't care what yarn is doing!

[Heartnett]

I agree with @TigersWay! From my side: I don't want a yarn clone.