@runfile/cli 1.1.6 → 1.2.0

package/README.md

@@ -817,9 +817,9 @@ actually decrypts, so a locked keyring never gets in the way of an unrelated tar
 
 ## Editor support
 
-`runfile-lsp` ships beside `run` and gives you diagnostics, completion, formatting, go-to-definition and
-documentation on hover — from the same parser `run` itself uses, so your editor never disagrees with what will
-actually happen.
+`run :lsp` is a language server, so the binary you already have gives you diagnostics, completion, formatting,
+go-to-definition and documentation on hover — from the same parser `run` itself uses, so your editor never
+disagrees with what will actually happen. There is nothing extra to install.
 
 Hover anything: a function shows its signature, what it does and a worked example; a property adds whether it
 may sit inside a block; `$`, `exec`, `run`, `retry`, `match` and the rest explain the line form itself.
@@ -838,8 +838,10 @@ same command in a `.sh` file. Set `"editor.formatOnSave": true` and saving forma
 **JetBrains IDEs** read the same grammar: *Settings → Editor → TextMate Bundles*, add the `editors/vscode`
 directory from a checkout.
 
-**Zed, Neovim and Helix** use the tree-sitter grammar in `editors/tree-sitter`, with highlight queries
-included. For Neovim with nvim-treesitter:
+**Zed, Neovim and Helix** point their language-server configuration at `run` with the argument `:lsp` — in
+Neovim, `vim.lsp.config("runfile", { cmd = { "run", ":lsp" }, filetypes = { "runfile" } })` — and take the
+tree-sitter grammar in `editors/tree-sitter` for highlighting, with highlight queries included. For Neovim
+with nvim-treesitter:
 
 ```lua
 require("nvim-treesitter.parsers").get_parser_configs().runfile = {

package/bin/run.js

@@ -2,10 +2,7 @@
 const path = require('node:path');
 const { spawnSync } = require('node:child_process');
 const KEY = process.platform + '-' + process.arch;
-// One launcher for both binaries, `run` and `runfile-lsp`: which one is
-// decided by this file's own name, so the second is a copy, not a second file.
-const NAME = path.basename(__filename, ".js");
-const EXE = process.platform === "win32" ? `${NAME}.exe` : NAME;
+const EXE = process.platform === "win32" ? "run.exe" : "run";
 const BINARIES = {
   "linux-x64": EXE,
   "linux-arm64": EXE,

package/package.json

@@ -1,7 +1,6 @@
 {
 	"bin": {
-		"run": "bin/run.js",
-		"runfile-lsp": "bin/runfile-lsp.js"
+		"run": "bin/run.js"
 	},
 	"description": "Runfile CLI — a cross-platform command runner with its own small language",
 	"engines": {
@@ -14,5 +13,5 @@
 	"license": "MIT",
 	"name": "@runfile/cli",
 	"repository": "https://github.com/JoaaoVerona/runfile",
-	"version": "1.1.6"
+	"version": "1.2.0"
 }

package/bin/runfile-lsp.js

@@ -1,32 +0,0 @@
-#!/usr/bin/env node
-const path = require('node:path');
-const { spawnSync } = require('node:child_process');
-const KEY = process.platform + '-' + process.arch;
-// One launcher for both binaries, `run` and `runfile-lsp`: which one is
-// decided by this file's own name, so the second is a copy, not a second file.
-const NAME = path.basename(__filename, ".js");
-const EXE = process.platform === "win32" ? `${NAME}.exe` : NAME;
-const BINARIES = {
-  "linux-x64": EXE,
-  "linux-arm64": EXE,
-  "darwin-arm64": EXE,
-  "darwin-x64": EXE,
-  "win32-x64": EXE,
-  "win32-arm64": EXE,
-};
-const bin = BINARIES[KEY];
-
-if (!bin) {
-	console.error(`run: unsupported platform ${KEY}. Supported: ${Object.keys(BINARIES).join(', ')}`);
-	process.exit(1);
-}
-
-const binPath = path.join(__dirname, KEY, bin);
-const result = spawnSync(binPath, process.argv.slice(2), { stdio: 'inherit' });
-
-if (result.error) {
-	console.error(`run: failed to spawn ${binPath}: ${result.error.message}`);
-	process.exit(1);
-}
-
-process.exit(result.status == null ? 1 : result.status);