How to keep dependency versions in sync across files?

[jbcpollak]

Lets say I have code like this:

foo.ts:

import { myDep } from "https://unpkg.com/[email protected]/myDep.ts"

bar.ts:

import { myDep } from "https://unpkg.com/[email protected]/myDep.ts"

How do I ensure my versions of myDep stay in sync across foo.ts and bar.ts?

Should Deno-idomatic code use dependency injection so dependencies are only externally referenced in one place? That seems like a good idea, but difficult to enforce.

[jedahan]

A few potential solutions:

• Subresource integrity for modules #200
• importing from a central file you run + code lint is another
• using a content-addressable protocol
• I'm pretty sure the current cache only updates on --reload and you can also pass in separate cache directories if you want, but I forget where I read that

In the spirit of #94, maybe this should be closed and re-addressed once deno is more mature?

[jbcpollak]

#200 might be a good duplicate for this ticket, seems like it plus 'central file to run' could have overlap (I was thinking of something like dependencies.ts).

#94 makes sense as well - Perhaps this is premature, but I was hoping this could be a place someone could lend a hand in defining.

[jedahan]

I think the enthusiasm and support is welcome but overwhelming at this stage. Its the downside of open development so early. Luckily, when #94 is closed, we can look at all the cross-references and reopen good discussions :)

[ry]

Thanks for the discussion. We'll revisit when this functionality is there in the rewrite. Closing this one.