Open
Description
A lot of deno-isms are very unstable as the Deno project's still in flux in a lot of ways. The additions of deno deploy specific APIs like Deno.kv, the addition of JSR, the npm compatibility work while. These are all great additions but completely change what one can expect to be in a module when one imports it.
Any one who writes ports shouldn't be exposed to that. Maximum longevity will be boon for any package ecosystem. We then should hide the Deno object from ghjkfiles and port manifests and instead provide a Ghjk or similar construct for IO and other concerns. I'd love to be able to cap the semantics of import as well but this seems impossible from within javascript.