You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
yarn's PnP solution: bind version with module, and use a resolver like .pnp.js to parse module version and module path.
python's solution: use requirements.txt to record package's version, use virtualenv to isolate different project(it could not isolate different version)
go mod solution?
Other solution?
The text was updated successfully, but these errors were encountered:
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.
It seems that deno has no version manager by far.
We could inject the version into our project code:
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?
.pnp.js
to parse module version and module path.requirements.txt
to record package's version, usevirtualenv
to isolate different project(it could not isolate different version)The text was updated successfully, but these errors were encountered: