Flaky installs when installing via yarn

[bienzaaron]

I'm seeing occasional installation failures for this package when installing via yarn 4, which is making my CI very flaky. It'll report errors like:

13:54:26  ➤ YN0000: │ @tusbar/cache-control@npm:1.0.1 STDERR npm WARN exec The following package was not found and will be installed: only-allow@1.2.1
13:54:26  ➤ YN0000: │ @tusbar/cache-control@npm:1.0.1 STDERR npm WARN exec The following package was not found and will be installed: only-allow@1.2.1
13:54:26  ➤ YN0000: │ @tusbar/cache-control@npm:1.0.1 STDERR sh: 1: only-allow: not found
13:54:26  ➤ YN0009: │ @tusbar/cache-control@npm:1.0.1 couldn't be built successfully (exit code 127, logs can be found here: /tmp/xfs-7e933b3f/build.log)

this is related to the preinstall script here:

cache-control/package.json

Line 30 in 49fda9c

"preinstall": "npx only-allow pnpm",

Some similar issues on different projects:
ethereum-optimism/optimism#9078
Sphereon-Opensource/PEX#157

This also could be related to some quirks in the way yarn 2+ run lifecycle scripts: https://yarnpkg.com/advanced/lifecycle-scripts#postinstall

Thoughts on removing this, or using corepack + the packageManager field to encourage contributors to use the correct package manager? Happy to send a PR if either are acceptable.

[bienzaaron]

Alternatively, a git precommit hook + running the only-allow script on a different script in this package's CI would also do the trick without the script running for consumers of this package.

[tusbar]

🎉 This issue has been resolved in version 1.0.2 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀