lucacasonato

We will soon support WASM imports (`import source foo from "./foo.wasm"`). [1]

[1]: https://github.com/tc39/proposal-source-phase-imports

You could also just use `String.prototype.padStart()` [1], and you get a nice optimized C++ implementation :D

[1]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

It does not use TSC / do type analysis. This is purely syntax analysis.

The "slow types" restriction specifically exists because JSR does not use TSC or do type analysis :)

1. You can bypass slow types checks during publishing. You will just get a lower JSR score.

2. TypeScript is shipping features in the next release (TS 5.5) has quick-fixes in the editor to make it super easy to add explicit types :) The TS feature is called `isolatedDeclarations`

The TypeScript syntax is very stable - there is no spec, but it's very stable. The type system on the other hand: not very stable, and yeah I agree - that would be risky to rely on.

However as JSR only relies on the syntax, not on the type system, it's no problem :)

You can use Queues for this :)

https://deno.com/blog/queues

Hey, I'm one of the developers working on Deno KV. Happy to answer questions!

I built this! Ask me things :D

Storage cost + write ops are multiplied by region count

Yes, Deno KV is much closer to D1 than to Cloudflare KV.

Thanks <3

Yes, the hosted KV solution built into Deno Deploy is one of the ways Deno makes money.

Yes, sort of - on Deno Deploy the authentication doesn't come from a token in env vars, but from intrinsic security tickets baked into the Deno Deploy system. Also, it's a bit faster on first connect, because compared to KV connect we can skip the metadata exchange[1] because the information it provides is already present in Deno Deploy through other means. Both the backend service and frontend API (JS->KV) is the same though :)

[1]: https://github.com/denoland/deno/blob/be1fc754a14683bf640b7b...

I worked on some of this - happy to answer questions :)

Check out https://wintercg.org

If you are same origin, you do not require CORS to use type=module. Also type=module works on HTML pages served from file:// (file:///.../index.html).

I don't think this will happen. People _love_ cutting edge innovation. Cutting edge innovation happens on cutting edge platforms, not in the legacy.

Most Node APIs work just like they do in Node, yes. Some are not yet implemented (like the ones you mentioned). We'll be addressing them in priority order based on user feedback and how many NPM packages are blocked by the given feature.

thanks! :D

Hey folks - I worked on this. AMA

JS runtime != JS engine

Runtime: - Chrome - Deno - Node - Bun

Engine: - V8 - JSC - SpiderMonkey - LibJS

All branch deployments share one store.

All main deployments share a different store.

Hey - I am one of the engineers that works on Deno KV. Happy to answer questions.

Well except for NPM :D

Our editor integration is completely editor agnostic. Deno implements the Language Server Protocol [1], which essentially all editors support. Because of this the new inlay hints feature, is supported on all editors that support inlay hints and use our LSP integration. The Jetbrains integration for Deno uses our LSP, but I don't know if they support inlay hints yet.

You can find docs on using Deno LSP with other editors here: https://deno.land/manual/getting_started/setup_your_environm...

[1]: https://microsoft.github.io/language-server-protocol/

It is not. It is a custom runtime on custom infrastructure. Why do you assume we use Cloudflare under the hood?

One of the next releases will improve the plugin API to the point where authentication providers can be very easily added as plugins.

It uses the Mozilla certificate store by default.

Are you behind a corporate firewall? Can you set `DENO_TLS_CA_STORE=system` and try again?

Thanks for the kind words!