denols cannot be used for single typescript

[Decodetalkers]

Description

nvim-lspconfig/lsp/denols.lua

Lines 107 to 126 in 43ed379

	root_dir = function(bufnr, on_dir)
	-- The project root is where the LSP can be started from
	local root_markers = { 'deno.lock', 'deno.json', 'deno.jsonc' }
	-- Give the root markers equal priority by wrapping them in a table
	root_markers = vim.fn.has('nvim-0.11.3') == 1 and { root_markers, { '.git' } }
	or vim.list_extend(root_markers, { '.git' })
	-- only include deno projects
	local deno_root = vim.fs.root(bufnr, { 'deno.json', 'deno.jsonc' })
	local deno_lock_root = vim.fs.root(bufnr, { 'deno.lock' })
	local project_root = vim.fs.root(bufnr, root_markers)
	if
	(deno_lock_root and (not project_root or #deno_lock_root > #project_root))
	or (deno_root and (not project_root or #deno_root >= #project_root))
	then
	-- deno config is closer than or equal to package manager lock,
	-- or deno lock is closer than package manager lock. Attach at the project root,
	-- or deno lock or deno config path. At least one of these is always set at this point.
	on_dir(project_root or deno_lock_root or deno_root)
	end
	end,

I just check the code, find now denols require always be used for a project dir, and nowadays we can also not control the root_marks, I wonder if it is by design

[Decodetalkers]

I have read the pr for it.. I do not think it is a clever fix for it. Before we can control the root_mark for them. but now there is not setting place for root_mark. But we can also choose if to enable them or not in our config, reading the root files in our config. Now it become a bug that event I write enable in the config, the lsp still cannot enable. Then it becomes a really bug I think

This is my solution in my config

https://github.com/Decodetalkers/nvim.dot/blob/next-lsp/lua/cmps/cmps_setup.lua#L161-L182

I think the fix for that is not a good fix, not to mention that deno also support package.json ad root mark