[no description] http://git.sudomsg.com/mirror/nvim-lspconfig/atom/lsp/biome.lua?h=v2.5.0 2025-09-18T03:07:52Z 2025-09-18T03:07:52Z Justin M. Keyes justinkz@gmail.com 2025-09-18T03:04:59Z urn:sha1:78174f395e705de97d1329c18394831737d9a4b4 Reverts 33e318a3f0e729fb7ee82619a21172712b0ea288 (except for svelte). fix #4074 close #4076 2025-09-11T03:31:23Z Alexis Tacnet alexis@mistral.ai 2025-09-11T03:31:23Z urn:sha1:ec54d14e0ad816e4099738a2b8f8e61ed3c9430e Problem: Some projects don't have a lockfile. Solution: - Fallback to ".git" as a lower-priority root-marker (Nvim 0.11.3+). - Fallback to CWD. 2025-09-03T12:21:40Z Kai Moschcau kai@kmoschcau.de 2025-09-03T12:21:40Z urn:sha1:33e318a3f0e729fb7ee82619a21172712b0ea288 Problem: `deno.lock` is not recognized as a root marker in JavaScript related servers. Solution: Add `deno.lock` as a root marker. 2025-08-22T01:31:43Z Justin M. Keyes justinkz@gmail.com 2025-08-22T01:31:43Z urn:sha1:8373a1b7a7ab7a9972b55182073be5ac2f3bec0a fix #4023 2025-08-20T16:31:19Z Oskar Haarklou Veileborg ohv1020@hotmail.com 2025-08-20T16:31:19Z urn:sha1:99748c019f214d2f4372094fe5766a616f27e124 2025-08-19T02:41:27Z Igor igorlfs@ufmg.br 2025-08-19T02:41:27Z urn:sha1:ec27b247a5e25f6997b66aee30090eda18efaa27 2025-08-19T02:39:23Z Igor igorlfs@ufmg.br 2025-08-19T02:39:23Z urn:sha1:030a72f0aa4d56f9e8ff67921e6e3ffd0e97bf07 2025-08-18T15:09:12Z Methapon2001 61303214+Methapon2001@users.noreply.github.com 2025-08-18T15:09:12Z urn:sha1:34c9ecfdcc19d579f51c072300a71445fbec9da8 2025-08-17T21:12:42Z Alexis Tacnet alexis@mistral.ai 2025-08-17T21:12:42Z urn:sha1:8ad2d8d8991d868ff8e7c21a7db624f32b882531 PROBLEM: Monorepos (or "workspaces") in Typescript are more and more popular and the associated tooling is evolving to improve the developer experience in such setup. Especially, the `typescript-language-server` and the `vscode-eslint-language-server` now supports monorepos, **removing the need to spawn a different server for each package of a workspace**. Example: with a few packages as the servers need to load every other package to work (the `typescript-language-server`, even if spawned multiple times with different `root_dir`, will load in memory other packages to resolve the types), the amount of memory used grows exponentially. But in fact, those servers support monorepos: they support multiple configurations in subpackages and will load the correct one to process a buffer. The ESLint server even supports loading multiple ESLint binaries (and therefore versions), while keeping one instance of the server. SOLUTION: Instead of only relying on the configuration files as `root_markers`, discover the root of the package / monorepo by finding the Lock files created by node package managers: * `package-lock.json`: Npm * `yarn.lock`: Yarn * `pnpm-lock.yaml`: Pnpm * `bun.lockb`: Bun We still need to look at configuration files to enable the conditionnaly attachment of the LSP for a buffer (for ESLint, we want to attach the LSP only if there are ESLint configuration files) in case of LSP that operates on files that are "generic" (like `typescript` or `javascript`). To do that, I replace the `root_markers` that were the configuration files by a `root_dir` function that superseds them. It will both: * look for a configuration file upward to check if the LSP needs to be attached * look for the root of the "project" via the lock files to specify the `root_dir` of the LSP PRIOR EXPERIMENTATIONS: I've tried to play with the `reuse_client` quite a lot, trying to understand if we need to spawn a new server or not looking at the Typescript / ESLint binary that was loaded, but in fact it's way easier to just have a better `root_dir` that is the true root of the project for the LSP server: in case of those two servers, the root of the package / monorepo. I also tried to use the current directory opened as the `root_dir`, but it's less powerful on nvim compared to VSCode as we navigate more inside folders using terminal commands and then open vim. I think this method also removes the need from a project-local config (which could be quite useful anyway for ESLint flat config setting which auto-detection is a bit unreliable / compute heavy) as this should work normally accross all different setups. Fixes #3910 2025-07-24T01:36:25Z Igor Lacerda igorlfs@ufmg.br 2025-07-24T01:36:25Z urn:sha1:169745f176f58becad80363c3f8f2315ed6bb365 The biome [documentation](https://biomejs.dev/guides/big-projects/#use-multiple-configuration-files) mentions that > When you use Biome’s features - either with the CLI or LSP - the tool looks for the nearest configuration file using the current working directory. > > If Biome doesn’t find the configuration file there, it starts traversing upwards the directories of the file system, until it finds one. I think it makes sense to follow this recommendation, so we can have proper monorepo support. Currently, in a monorepo, a new client is started for each `biome.json` (similar situation as #3910), which is unnecessary, since biome supports monorepos [natively](https://biomejs.dev/guides/big-projects/#monorepo) (as of v2). The alternatives I have considered aren't as robust. The first concern is searching for a `biome.json` to be set as the root. Unfortunately, that's cumbersome: the documentation recommends flagging the files that _aren't_ the root. That means we _can't_ use `root_markers_with_field` to search for a file that **is** the root. The proposed solution solves this issue by behaving as the CLI would. Secondly, we have to check if a project uses biome, via `package.json` and friends, which is the fallback behavior. I've considered using #3955's approach of lock files, but since it would require searching for the field 'biome' within lock files (which are often thousands of lines long), I was worried about causing a performance hiccup. 2025-07-19T15:29:49Z Chris Grieser 73286100+chrisgrieser@users.noreply.github.com 2025-07-19T15:29:49Z urn:sha1:24edc2b87786b921276d092d9e7d8202d0cdf259 2025-07-19T01:43:57Z Igor Lacerda igorlfs@ufmg.br 2025-07-19T01:43:57Z urn:sha1:33898a06457b1074a3846958233d29c9ee191cb5 2025-06-18T12:23:47Z Chris Grieser 73286100+chrisgrieser@users.noreply.github.com 2025-06-18T12:23:47Z urn:sha1:18ad378b95842206e0cc53ed45994f1ac0666f24 The latest release of biome adds prelimanary support for formatting html files https://biomejs.dev/blog/biome-v2/#html-formatter Thus, html should be added to the list of filetypes for the biome LSP. 2025-04-18T15:44:38Z Justin M. Keyes justinkz@gmail.com 2025-04-18T15:44:38Z urn:sha1:f8b5cbe6312b568def1f91d747e2cdb8984fdf2e - brief should live at the top of each file - fix indentation for some docs 2025-04-15T13:26:49Z Chris Grieser 73286100+chrisgrieser@users.noreply.github.com 2025-04-15T13:26:49Z urn:sha1:4cb35c04d36efb1a393bce38d40689a76b0c3d62 2025-04-13T21:35:29Z Chris Grieser 73286100+chrisgrieser@users.noreply.github.com 2025-04-13T21:35:29Z urn:sha1:2c897a02c65f9d4cdbd6609f8e5add1d14fceae1 This reverts commit cd54cca6c4a03b89f2a82e32ae6bfc230b5b4193. 2025-04-13T12:47:12Z Chris Grieser 73286100+chrisgrieser@users.noreply.github.com 2025-04-13T12:47:12Z urn:sha1:cd54cca6c4a03b89f2a82e32ae6bfc230b5b4193