@valbuild/language-server 0.113.0 → 0.115.0

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

@@ -1524,20 +1524,22 @@ function createValCommands(deps) {
       connection
     } = deps;
     try {
-      const session = await server.startValLogin();
+      const authorization = await server.startValLogin();
       // `showDocument` with `external` is the standard way to reach a browser;
       // there is no Val-specific request for it, which is what lets any LSP
       // client drive this flow.
       await connection.sendRequest(vscodeLanguageserver.ShowDocumentRequest.type, {
-        uri: session.url,
+        uri: authorization.verificationUriComplete,
         external: true
       });
-      // The poll runs for up to five minutes. Without progress the editor looks
+      // The poll runs until the code expires. Without progress the editor looks
       // hung, and there is nothing to tell the user the browser is the next step.
-      const progress = await withProgress(connection, "Val: waiting for login", "Complete the login in your browser.");
+      // The user code goes in the message so it can be compared against what the
+      // browser shows — that comparison is what makes approving safe.
+      const progress = await withProgress(connection, "Val: waiting for login", `Approve the login in your browser. Code: ${authorization.userCode}`);
       let confirmed;
       try {
-        confirmed = await server.awaitValLoginConfirmation(session.nonce, {
+        confirmed = await server.awaitValLoginConfirmation(authorization, {
           signal: progress.signal
         });
       } finally {

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

@@ -1524,20 +1524,22 @@ function createValCommands(deps) {
       connection
     } = deps;
     try {
-      const session = await server.startValLogin();
+      const authorization = await server.startValLogin();
       // `showDocument` with `external` is the standard way to reach a browser;
       // there is no Val-specific request for it, which is what lets any LSP
       // client drive this flow.
       await connection.sendRequest(vscodeLanguageserver.ShowDocumentRequest.type, {
-        uri: session.url,
+        uri: authorization.verificationUriComplete,
         external: true
       });
-      // The poll runs for up to five minutes. Without progress the editor looks
+      // The poll runs until the code expires. Without progress the editor looks
       // hung, and there is nothing to tell the user the browser is the next step.
-      const progress = await withProgress(connection, "Val: waiting for login", "Complete the login in your browser.");
+      // The user code goes in the message so it can be compared against what the
+      // browser shows — that comparison is what makes approving safe.
+      const progress = await withProgress(connection, "Val: waiting for login", `Approve the login in your browser. Code: ${authorization.userCode}`);
       let confirmed;
       try {
-        confirmed = await server.awaitValLoginConfirmation(session.nonce, {
+        confirmed = await server.awaitValLoginConfirmation(authorization, {
           signal: progress.signal
         });
       } finally {

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

@@ -1513,20 +1513,22 @@ function createValCommands(deps) {
       connection
     } = deps;
     try {
-      const session = await startValLogin();
+      const authorization = await startValLogin();
       // `showDocument` with `external` is the standard way to reach a browser;
       // there is no Val-specific request for it, which is what lets any LSP
       // client drive this flow.
       await connection.sendRequest(ShowDocumentRequest.type, {
-        uri: session.url,
+        uri: authorization.verificationUriComplete,
         external: true
       });
-      // The poll runs for up to five minutes. Without progress the editor looks
+      // The poll runs until the code expires. Without progress the editor looks
       // hung, and there is nothing to tell the user the browser is the next step.
-      const progress = await withProgress(connection, "Val: waiting for login", "Complete the login in your browser.");
+      // The user code goes in the message so it can be compared against what the
+      // browser shows — that comparison is what makes approving safe.
+      const progress = await withProgress(connection, "Val: waiting for login", `Approve the login in your browser. Code: ${authorization.userCode}`);
       let confirmed;
       try {
-        confirmed = await awaitValLoginConfirmation(session.nonce, {
+        confirmed = await awaitValLoginConfirmation(authorization, {
           signal: progress.signal
         });
       } finally {

package/package.json

@@ -11,7 +11,7 @@
     "lsp",
     "language-server"
   ],
-  "version": "0.113.0",
+  "version": "0.115.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.113.0",
-    "@valbuild/shared": "0.113.0",
-    "@valbuild/core": "0.111.0"
+    "@valbuild/core": "0.111.0",
+    "@valbuild/server": "0.115.0",
+    "@valbuild/shared": "0.114.0"
   },
   "devDependencies": {
     "@types/jest": "^30.0.0",