Deno Deploy so far feels a lot closer though. For instance, CFW forces you to bundle your code into 1 js file, whereas with Deno Deploy you can just point to an

Deno Deploy so far feels a lot closer though. For instance, CFW forces you to bundle your code into 1 js file, whereas with Deno Deploy you can just point to an arbitrary .js hosted anywhere on the internet, and any transitive dependencies will be fetched and cached for subsequent runs. It doesn't support dynamic imports yet, but fingers crossed that's on the roadmap. UPDATE: apparently CFW has been updated to support deploying as unbundled files since I last checked.