[Discussion]What's the best version manager for deno package?

[ahuigo]

It seems that deno has no version manager by far.
We could inject the version into our project code:

    import mod from 'mod/v0.1.1/main.ts';

It's painful as we have to write version everywhere. if we want to upgrade our package, replace the version is painful too.

So, what's the best version manager for deno package?

1. yarn's PnP solution: bind version with module, and use a resolver like .pnp.js to parse module version and module path.
2. python's solution: use requirements.txt to record package's version, use virtualenv to isolate different project(it could not isolate different version)
3. go mod solution?
4. Other solution?

[nayeemrmn]

Read the bottom section in https://deno.land/std/manual.md#linking-to-third-party-code.

[hayd]

A tool for updating versioned urls: https://github.com/hayd/deno-udd
But agree that using deps.ts makes things easier.

[jtheisen]

@nayeemrmn Link is broken.

[nayeemrmn]

https://deno.land/manual@v1.7.5/linking_to_external_code#it-seems-unwieldy-to-import-urls-everywhere

[ivawzh]

Wouldn't deps.ts make optimization (like code-split) hard?
Also, we will need to care about naming collisions, almost like global unique names for each 3rd party function.
Package source URL is forbidden to changes in the future too.