What you're saying doesn't make sense. Caret means nothing when you just install a package fresh (you always get latest) and when you already installed then the version is now pinned using a lockfile.

Carets and other versioning schemes are only when you upgrade.

Semantics are important :-)

Good call outs. I'll take a look at adding them in next week. Thanks Jay ❤️

Em Hamoshavot ❤️

probably detected you're an ultra slow reader
😆

They do, it's called a lockfile :-)

:)

So cool Keviv!

It's under Reports. If you're on the free plan it's not there, see here: docs.snyk.io/manage-risk/...

there's a deep dive here: pnpm.io/supply-chain...

Always

Good work 👏

My point remains - if I'm using it in my app.js but my app is actually part of a framework, which actually already reads .env with its own dotenv, so effectively when the f/w reads "run op://..." then it would fail

you're absolutely right

but for real, of course, the only thing I remember in bash is if statements go inside square brackets. oh and the ; termination and the fi closing statement

and speaking as someone who wrote bash for a living, for real