Unexpectedly ts_ls stating at deno workspace

[kuuote]

Description

Deno typically uses denols. This is because Deno's import mechanism is special, and it won't function properly even if ts_ls is running.

This issue was introduced in #4051. Since this seems like an unusual situation, would it be okay if I submit a PR to revert it for now?

[kawarimidoll]

I agree. Just as #3955 wasn't intended for denols, Deno projects should be considered distinct from Node projects.
I don't think ts_ls, tsgo and other Node LSPs should use deno.lock as their root_marker.

[justinmk]

I was hoping that @kmoschcau actually had a valid reason for this, but it seems like I need to start asking if people know wtf they are doing when they make changes. Apparently that question is not implied.

[kmoschcau]

I did have a valid reason with the svelte server crashing in projects that were set up with deno, because it did not find a root directory. The changes I made fixed that problem for me and I did not have problems when I tested those changes locally, neither with svelte or the other servers.

My assumption was wrong that this meant it would work for all projects. So by all means revert it. I'm not using deno anymore for these projects anyway.

[kmoschcau]

I opened #4076 to revert this. @kawarimidoll @kuuote I removed the marker from everything again. If there are some servers (like potentially svelte), that do work with deno, the markers have to be put back separately.

[kuuote]

Thank you for doing that.