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

Created on 8 Mar 2020  路  2Comments  路  Source: denoland/deno

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?

Most helpful comment

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

All 2 comments

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

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ry picture ry  路  3Comments

ry picture ry  路  3Comments

xueqingxiao picture xueqingxiao  路  3Comments

benjamingr picture benjamingr  路  3Comments

justjavac picture justjavac  路  3Comments