it shouldnt be pinned. otherwise we're forcing deno users to pin/hold onto a stale version for basic path-module imports

Deno best practice recommends that all imports be versioned, hence the warning from deno that I noted above.

I understand the desire to "keep current". But, as deno doesn't concern itself with semantic versioning for imports, using floating "latest" versions will eventually cause breakage for an imported module. And pinning in this module doesn't affect any other module; it only makes sure that this module will continue to work as written today.

For any production grade application, all the dependencies must be versioned. There is no exception to this. Keeping it un-versioned would download the latest code, and it may not be compatible with current application code.

Never use un-versioned dependencies

ref: https://medium.com/deno-the-complete-reference/dependency-management-in-deno-48f1c91ad84d

... it is a warning that you are implicitly using a version which is risky. You are welcome to ignore the warning.

• kitsonk

however, it's fairly standard practice to import standard libraries using the latest version isn't it?

Not really. All imports should always be versioned.

• lucacasonato

ref: denoland/deno#10822

@lukeed , no further discussion?

@lukeed , I believe the problem you are concerned about doesn't exist.
But if you're not comfortable with the change, I'll recommend vendoring a corrected version for yargs.

☠️ ⚰️