You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bun follows the same lifecycle scripts outlined in NPM docs, but PNPM runs both scripts when using pnpm publish. But if you scroll further up in NPM docs, you'll (still) read this:
As of [email protected], a new event has been introduced, prepare, that preserves this existing behavior. A new event, prepublishOnly has been added as a transitional strategy to allow users to avoid the confusing behavior of existing npm versions and only run on npm publish (for instance, running the tests one last time to ensure they're in good shape).
See npm/npm#10074 for a much lengthier justification, with further reading, for this change.
And in the issue there's a plan outlined, which is still missing 1 or 2 steps:
In a year or so, make a semver-major bump to npm and make prepublish's behavior match prepublishOnly.
Either then or sometime after that, deprecate prepublishOnly and have just prepare and prepublish.
Seems like we're still stuck in a "transitional" state, having both prepublishOnly and prepublish while still "planning" to finish it but still supporting the old, confusing prepublish script behavior in install.
The text was updated successfully, but these errors were encountered:
Bun follows the same lifecycle scripts outlined in NPM docs, but PNPM runs both scripts when using
pnpm publish
. But if you scroll further up in NPM docs, you'll (still) read this:And in the issue there's a plan outlined, which is still missing 1 or 2 steps:
Seems like we're still stuck in a "transitional" state, having both
prepublishOnly
andprepublish
while still "planning" to finish it but still supporting the old, confusingprepublish
script behavior ininstall
.The text was updated successfully, but these errors were encountered: