WARNING THis goes contrary to Deno philosophy of no package.json dependencies.
This Article from dev.to desrcibes a way to keep packages updated (or at least notify you if package needs updating).
But there's already an existing tool called npm. How can we take advantage of npm to distribute deno packages. Among other things, since deno acts from cdns, you can also
We can piggyback off the work of npm! NPM downloadas the package into the node_modules,
and a new tool/script somewhere there (still to be written) can run which checks an imports file if there are updates to the deno package.
Not exactly the global stylesheets, but on an organism level (instead of atomic/component level). You can separate the CSS into an object and "inject" (like how react-styled / jsx works). I think the whole idea is that instead of using jsdeliver to share your css, you have the "object styles" in your own servers, ready for consumption by s any framework that can decode / map it to your component.
Think shareable themes, not really webcomponents.
We usually have to use python SimpleHTTPServer to run a website html. With deno, static file serving using their server thing is a sinch. Found a gist already on this - https://gist.github.com/kitsonk/f8210d2f802a0e5396abda32552be0dc . Deno looks able to serve my html files without the need for an nginx!