Kitson Kelly
Kitson Kelly
Can you provide the output of `deno --version` of the version of Deno you are using as an lsp. Also what editor and version of the editor you are using...
This is still really hard, as we have been unable to successfully get ES module loading and snapshots working as well. This likely ends up in the "too hard" bin.
IMO, this is something that should start external to Deno/`std` and move into `std`. It should either be a native module or Web Assembly.
HTTP2 will eventually land. Again, this needs to start as something seperate from `std` or the Deno cli.
To give context, we believe that integrated gRPC to the Deno CLI is an important feature and are committing core team resources to delivering it.
ARM64 support was reverted some time ago... re-opening.
> FYI, not sure if deno is using Travis CI in conjunction with github but Travis CI We use GitHub Actions exclusively. We are working with GitHub on the potential...
There are lots of things the devs can do. We have priorities though that may not align to each individuals priorities.
Technically this shouldn't be happening, it should be coming in with the import completion already remapped.
@isLishude then you are probably looking at the wrong project.