@valbuild/language-server 0.132.0 → 0.133.0

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # @valbuild/language-server
 
+## 0.133.0
+
+### Patch Changes
+
+- Updated dependencies [[`802412b`](https://github.com/valbuild/val/commit/802412b92c06bc1abbca78c86885e39c8710dd83)]:
+  - @valbuild/server@0.133.0
+  - @valbuild/shared@0.133.0
+
+## 0.132.1
+
+### Patch Changes
+
+- [#685](https://github.com/valbuild/val/pull/685) [`f2ac188`](https://github.com/valbuild/val/commit/f2ac1887c11397b597081eef7206063b52b21c5b) Thanks [@freekh](https://github.com/freekh)! - Editor clients: resolve the language server through `@valbuild/tanstack` too
+
+  `@valbuild/language-server` ships inside Val's framework bindings and its CLI —
+  `@valbuild/next`, `@valbuild/tanstack` and `@valbuild/cli` — but the resolution
+  recipes in this package's README, which exist to be copied into an editor
+  client, only ever anchored on `next` and `cli`.
+
+  Under pnpm's isolated `node_modules` a transitive dependency is reachable _only_
+  through a package the project declares, so a client built from those snippets
+  finds nothing at all in a TanStack Start project. The Neovim configuration in
+  here then tells the user to upgrade `@valbuild/next` — a package they do not
+  have and should not add.
+
+  The snippets now anchor on `@valbuild/tanstack` as well, and point at the better
+  version of the rule: read the project's own `@valbuild/*` dependencies out of its
+  `package.json` and try those first, so the framework binding after this one works
+  with no client release. Docs only — the server itself is unchanged, and the VS
+  Code extension already resolved this way.
+
+- Updated dependencies [[`c07b1ab`](https://github.com/valbuild/val/commit/c07b1abe30e226c80ef7ec4b4f0f5ccdae061c11), [`cbfa2b8`](https://github.com/valbuild/val/commit/cbfa2b884898f1603bde8e5aa5cd9da78778101f)]:
+  - @valbuild/server@0.132.1
+
 ## 0.132.0
 
 ### Patch Changes

package/README.md

@@ -3,9 +3,11 @@
 The Val language server: validation, quick fixes and completions for `*.val.ts`
 files, over the Language Server Protocol.
 
-It ships **inside Val**, as a dependency of `@valbuild/next` and
-`@valbuild/cli`. You do not install it — a project on a recent enough Val
-already has it. That is the point: an editor client resolves the server out of
+It ships **inside Val**, as a dependency of the framework bindings and the CLI —
+`@valbuild/next`, `@valbuild/tanstack` and `@valbuild/cli`. Not of every
+`@valbuild/*` a project depends on: `@valbuild/core` and `@valbuild/server`
+could not carry it without a cycle, since the server depends on them. You do not
+install it — a project on a recent enough Val already has it. That is the point: an editor client resolves the server out of
 the user's own `node_modules`, so one published client works against every
 version of Val, and a feature Val gains works without an editor release.
 
@@ -45,18 +47,34 @@ import { createRequire } from "node:module";
 
 const rootPkg = path.join(projectRoot, "package.json");
 // A direct dependency wins; otherwise go through whichever package carries it.
-// @valbuild/core and @valbuild/server are NOT valid anchors -- they do not
-// depend on the language server, and could not without a cycle.
-for (const anchor of [null, "@valbuild/next", "@valbuild/cli"]) {
-  const from =
-    anchor === null
-      ? rootPkg
-      : createRequire(rootPkg).resolve(`${anchor}/package.json`);
-  const pkgPath = createRequire(from).resolve(
-    "@valbuild/language-server/package.json",
-  );
-  const pkg = JSON.parse(fs.readFileSync(pkgPath, "utf8"));
-  return path.resolve(path.dirname(pkgPath), pkg.bin["val-language-server"]);
+// One anchor per framework binding, plus the CLI. @valbuild/core and
+// @valbuild/server are NOT valid anchors -- they do not depend on the language
+// server, and could not without a cycle. Better still: read the project's own
+// @valbuild/* dependencies out of its package.json and try those first, so a
+// framework package added after your client shipped resolves anyway.
+for (const anchor of [
+  null,
+  "@valbuild/next",
+  "@valbuild/tanstack",
+  "@valbuild/cli",
+]) {
+  // The try/catch is load-bearing, not defensive: `resolve` THROWS when it
+  // finds nothing. Under pnpm the first (`null`) attempt is exactly that case,
+  // so without it the anchors below are never reached and the recipe fails on
+  // the one layout it exists for.
+  try {
+    const from =
+      anchor === null
+        ? rootPkg
+        : createRequire(rootPkg).resolve(`${anchor}/package.json`);
+    const pkgPath = createRequire(from).resolve(
+      "@valbuild/language-server/package.json",
+    );
+    const pkg = JSON.parse(fs.readFileSync(pkgPath, "utf8"));
+    return path.resolve(path.dirname(pkgPath), pkg.bin["val-language-server"]);
+  } catch {
+    // Not reachable through this anchor. Try the next.
+  }
 }
 ```
 
@@ -238,7 +256,7 @@ local RESOLVE = [[
 const { createRequire } = require("node:module");
 const fs = require("fs"), path = require("path");
 const rootPkg = path.join(process.argv[2], "package.json");
-for (const anchor of [null, "@valbuild/next", "@valbuild/cli"]) {
+for (const anchor of [null, "@valbuild/next", "@valbuild/tanstack", "@valbuild/cli"]) {
   try {
     const from = anchor === null
       ? rootPkg
@@ -269,7 +287,7 @@ local function val_server_cmd(root)
   -- its dependencies are not installed. Say so rather than starting nothing.
   vim.notify(
     "Val: no @valbuild/language-server in " .. root ..
-      " -- upgrade @valbuild/next or @valbuild/cli.",
+      " -- upgrade @valbuild/next, @valbuild/tanstack or @valbuild/cli.",
     vim.log.levels.WARN
   )
   return nil

package/dist/valbuild-language-server.cjs.dev.js

@@ -183,7 +183,7 @@ var packageJson = {
 		"lsp",
 		"language-server"
 	],
-	version: "0.132.0",
+	version: "0.133.0",
 	bin: {
 		"val-language-server": "./bin.js"
 	},

package/dist/valbuild-language-server.cjs.prod.js

@@ -183,7 +183,7 @@ var packageJson = {
 		"lsp",
 		"language-server"
 	],
-	version: "0.132.0",
+	version: "0.133.0",
 	bin: {
 		"val-language-server": "./bin.js"
 	},

package/dist/valbuild-language-server.esm.js

@@ -172,7 +172,7 @@ var packageJson = {
 		"lsp",
 		"language-server"
 	],
-	version: "0.132.0",
+	version: "0.133.0",
 	bin: {
 		"val-language-server": "./bin.js"
 	},

package/package.json

@@ -11,7 +11,7 @@
     "lsp",
     "language-server"
   ],
-  "version": "0.132.0",
+  "version": "0.133.0",
   "bin": {
     "val-language-server": "./bin.js"
   },
@@ -29,9 +29,9 @@
     "typescript": "^6.0.3",
     "vscode-languageserver": "^10.1.0",
     "vscode-languageserver-textdocument": "^1.0.14",
-    "@valbuild/server": "0.132.0",
-    "@valbuild/shared": "0.130.0",
-    "@valbuild/core": "0.130.0"
+    "@valbuild/core": "0.130.0",
+    "@valbuild/server": "0.133.0",
+    "@valbuild/shared": "0.133.0"
   },
   "devDependencies": {
     "@types/jest": "^30.0.0",