| ▲ | king_zee 2 hours ago | |||||||
I've made it a habit now to use the --before=2026-05-30 flag when installing packages, where it'll pick the version released before the date you specify, I usually pick around 5 days ago | ||||||||
| ▲ | t-sauer an hour ago | parent | next [-] | |||||||
If you use npm 11, you can simplify your workflow by setting min-release-age to 5. https://docs.npmjs.com/cli/v11/using-npm/config#min-release-... | ||||||||
| ▲ | mihaelm an hour ago | parent | prev | next [-] | |||||||
I just use `pnpm` and set up a liberal `minimumReleaseAge`: https://pnpm.io/settings#minimumreleaseage Thankfully, it's on by default since v11. | ||||||||
| ▲ | sync an hour ago | parent | prev | next [-] | |||||||
If using straight npm (v11.10.0 or higher), you can just add to .npmrc in the project root: min-release-age=5 | ||||||||
| ▲ | sourcegrift 2 hours ago | parent | prev [-] | |||||||
Yarn 4 can automate this | ||||||||
| ||||||||