It's easy to begin development with the wrong dependencies installed. Here's some examples:
Normally you'd have to remember to run pnpm i
in these scenarios. I'd like pnpm to "remember" for me.
Before I run a script in the "scripts"
field of the package.json
(or pnpm test
, etc.), I'd like pnpm to check that the correct dependencies are installed then either:
pnpm i
pnpm i
in the background).pnpm i
can pose security risks (because postinstall
scripts can run arbitrary code), so doing this should be opt-in on the developer-level in my opinion.Keep the status quo.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4