> ...pretty much any functionality provided to deno is available for node as well.
replyUnfortunately Node still can't do something like this out of the box (AFAIK at least):
import { Bla } from "npm:bla@^5";
Deno also has a builtin TS type checker, linter, formatter, test runner with coverage support, package manager, language server etc etc... In node these are all separate (and often 3rd-party) tools.
This doesn't seem like a big deal. Don't you just npm install whatever you need and then change the import names?
replyI don't want the install step. That's redundant. Just a .ts script I can run via `deno run bla.ts` and which directly pulls in any dependency it needs from the web.
replyBun has auto-install for you, but you do have to enable it.
replyI understand the point of this, just saying an existing codebase importing things this way doesn't seem all that hard to convert if you need to get off Deno.
replyFWIW, almost this exact syntax for imports (without the `npm:` prefix) is supported for standalone scripts with Bun.
replyBun is not an alternative, it was also acquihired and will probably become an internal project of Anthropic for claude code.
replythis one is actually a bad pattern to avoid.
replyOnly when you have no control over the version you're pulling in, but the semver resolution works as expected. Also we're talking about small standalone 'shell scripts', not 'real projects'. Think 'bla.sh', just with a .ts extension. Deno is really great for such small helper scripts.
reply[dead]
reply