this is an experiment to see what happens on val.town when importing from another val and the api changes.
I think there's a versioning story, but for this unversioned usage it seems to act as a rug-pull. What's weird to me is that I'm getting a type error but it seems to execute an old version because there is no runtime error after the api change.
so there are magic redirects happening - https://docs.val.town/reference/esm-town/
it'd be good if the real version showed on hover or something. Also, the type definitions imported need to match this logic.
Another idea: Maybe the imports would be better added to a deno.json that comes with some sort of version management UI making upgrades and version inspectability trivial. They could still be auto-added from the editor, but then the UI just edits the deno.json instead of the current file. The thing that this breaks is that it assumes that you're not using multiple versions of a dep for a given val, but that seems to have more upside than down.