Results 173 comments of Bedis Nbiba

Is it possible to run the examples here https://preactjs.com/guide/v10/preact-testing-library/ using this trick? I tested a bit screen api seems to fail. and also I had to use npm jsdom because...

for jsdom I imported it with npm:jsdom and I had to patch `vm.isContext` to return false (https://github.com/denoland/deno/issues/18315)

Nope I got the same errors

I did it in a hacky way but I saw Industrial has a better method https://discord.com/channels/684898665143206084/1022163295895027722/threads/1025572387695108187 ![image](https://user-images.githubusercontent.com/22427111/195670085-457c57d2-c149-4b21-90a2-b655d1c3166c.png)

You can listen to sigint signal and do the cleanup there

This probably belongs to a separate plugin.

deno puppeteer also requires run-all because of this

Regarding >relative dependencies inside virtual text document is not resolved correctly The problem is in virtual text nvim automatically adds the current file-path to deno schema so `deno:/https/deno.land/x/simple_shell%400.13.0/mod.ts` becomes `/home/user/dev/deno:/https/deno.land/x/simple_shell%400.13.0/mod.ts`

Currently there is only one bug remaining https://github.com/neovim/neovim/pull/19967 with that fixed the experience is equivalent to vscode-deno The missing features can be implemented in a separate plugins once this bug...

I wrote a plugin for this https://github.com/sigmaSd/deno-nvim