David Sherret

~~@ry I would use them in the version manager I'm working on to help generate these files https://bvm.land/deno/1.3.2.json which are used to install versions of deno.~~ Edit: I don't need...

Going to revert this one in https://github.com/dsherret/ts-morph/pull/1595 -- Maybe in a few years once things have played out with tinyglobby I'll switch back to that.

I agree on adding this. It would be nice if this mode also didn't store anything in the lockfile that's not found in the deno.json/package.json

Actually, I just realized the documentation is here: https://docs.deno.com/runtime/reference/cli/task/#environment-variables But it might be nice to list `export` under built-in commands anyway.

Can you show an example? Deno should already allows npm packages to work without the `node:` specifier.

What version of the extension are you using? What operating system/architecture do you have? Does your node_modules folder have a dprint executable in it? What happens if you run `npx...

Does it work with version 0.16.2? Do you think https://github.com/dprint/dprint-vscode/pull/92 broke it? Specifically https://github.com/dprint/dprint-vscode/pull/92/files#diff-cadc1bd035f997fef1cdf057f2016ed0cfeb8b602903fceacca2e3d2363b8c67R20 Are you on aarch64 windows or x86-64?

@MohammadSu1 can you push the failing test to the PR?

I just managed to type the above comment on the review page between my browser freezing lol. Reviewed by looking at a git diff of this PR against main. Thanks...

> Same issue here. It works fine to run code like deno run however it makes deno test failed due to `ERR_TYPES_NOT_FOUND`. Any workaround ? The workaround atm is to...