@nudojs/lsp 0.3.0 → 0.4.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nudojs/lsp",
-  "version": "0.3.0",
+  "version": "0.4.1",
   "description": "Language Server Protocol implementation for the Nudo type inference engine",
   "type": "module",
   "license": "MIT",
@@ -11,7 +11,17 @@
     "lsp",
     "language-server"
   ],
-  "main": "src/server.ts",
+  "main": "./dist/server.js",
+  "types": "./dist/server.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/server.d.ts",
+      "default": "./dist/server.js"
+    }
+  },
+  "files": [
+    "dist"
+  ],
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nudojs/nudo.git",
@@ -27,9 +37,9 @@
   "dependencies": {
     "vscode-languageserver": "^9.0.0",
     "vscode-languageserver-textdocument": "^1.0.0",
-    "@nudojs/service": "0.2.1",
-    "@nudojs/core": "0.2.0",
-    "@nudojs/parser": "0.2.0"
+    "@nudojs/service": "0.3.1",
+    "@nudojs/core": "0.3.1",
+    "@nudojs/parser": "0.3.1"
   },
   "scripts": {
     "build": "tsup src/server.ts --format esm --dts"

package/CHANGELOG.md

@@ -1,41 +0,0 @@
-# @nudojs/lsp
-
-## 0.3.0
-
-### Minor Changes
-
-- 0fd0718: Merge the three environment packages into one: `@nudojs/env-es`, `@nudojs/env-web`, `@nudojs/env-node` are replaced by a single `@nudojs/env` package with subpath exports `@nudojs/env/es`, `@nudojs/env/web`, `@nudojs/env/node`.
-
-  Move agent-facing tools from the standalone MCP server into the language server: `@nudojs/mcp` is removed. `@nudojs/lsp` now exposes `nudo.whatIf`, `nudo.suggestCase`, `nudo.trace`, `nudo.selectCase`, and `nudo.getActiveCases` via `workspace/executeCommand` (custom-request aliases `nudo/whatIf` etc. included), adds pull-mode diagnostics, and works on files that are not open in the editor (disk fallback). `nudo.whatIf` now actually applies the given type bindings — previously they were ignored. AI agents connect through any LSP↔MCP bridge (cclsp, mcpls, agent-lsp) or a native LSP client; an installable agent skill ships at `packages/lsp/agent-skill/SKILL.md`.
-
-### Patch Changes
-
-- @nudojs/service@0.2.1
-
-## 0.2.0
-
-### Minor Changes
-
-- 6c38283: docs and ci
-- 9f7f819: fix pkg info
-- c175f71: version
-
-### Patch Changes
-
-- Updated dependencies [6c38283]
-- Updated dependencies [9f7f819]
-- Updated dependencies [c175f71]
-  - @nudojs/core@0.2.0
-  - @nudojs/service@0.2.0
-
-## 0.1.0
-
-### Minor Changes
-
-- Conceptual design and basic implementation.
-
-### Patch Changes
-
-- Updated dependencies
-  - @nudojs/core@0.1.0
-  - @nudojs/service@0.1.0

package/agent-skill/SKILL.md

@@ -1,83 +0,0 @@
----
-name: nudo
-description: Query precise JavaScript types by abstract interpretation — use when the project uses Nudo (@nudo: directives) and you need the inferred type of a variable or expression, a function's input→output type trace, what-if type hypotheses, case coverage, or type diagnostics for a .js file.
----
-
-# Nudo — type inference for JavaScript
-
-Nudo is a comment-driven type inference engine for plain JavaScript. It derives types by **executing** code with symbolic type values (`T.number`, `T.string`) instead of requiring TypeScript annotations: functions marked with `@nudo:case` directives are run under abstract interpretation, and unmarked functions get cases synthesized from their call sites (whole-program inference). Ask Nudo instead of guessing what a refactor does to types.
-
-## Install and connect
-
-Nudo's agent face lives in its language server. Install it in the user's project (or globally):
-
-```bash
-npm i @nudojs/lsp          # project-local; or: npm i -g @nudojs/lsp
-```
-
-The server speaks LSP over stdio:
-
-```bash
-node node_modules/@nudojs/lsp/src/server.ts   # Node >= 22.18; on older Node: npx tsx <path>
-```
-
-Three ways to connect (details in the [Agent Integration Guide](https://nudojs.github.io/nudo/docs/guides/mcp-server)):
-
-1. **Generic LSP→MCP bridge** (cclsp, mcpls, agent-lsp) — registers Nudo as the language server for `.js` files; verify the bridge passes through `workspace/executeCommand`.
-2. **Native LSP client** — spawn the server over stdio, `initialize`, then call `workspace/executeCommand` (or the custom request aliases below).
-3. **VS Code / Cursor** — the `nudo-vscode` extension launches the server automatically.
-
-## Command cheat sheet
-
-All commands are available as `workspace/executeCommand` (dot form) and as custom LSP requests (slash form); agents use the `file` parameter everywhere (accepts a `file://` URI or a bare path). Editor extensions call the `nudo/selectCase` / `nudo/getActiveCases` requests with editor-style `uri` params instead — same handlers. Files that are not open in an editor are read from disk. `whatIf`, `suggestCase`, and `trace` return MCP-style text content — `{ content: [{ type: "text", text }] }`.
-
-| Command (request alias) | Arguments (JSON) | Returns |
-|---|---|---|
-| `nudo.whatIf` (`nudo/whatIf`) | `{ "file": "src/app.js", "bindings": [{ "name": "x", "type": "string" }], "target": "y" }` | Text: the inferred type of `target` **under the assumed bindings** — e.g. `Type of "y": string \| number` |
-| `nudo.trace` (`nudo/trace`) | `{ "file": "src/app.js", "functionName": "parse" }` | Text: one line per case, e.g. `Input: (T.string) => Output: number` |
-| `nudo.suggestCase` (`nudo/suggestCase`) | `{ "file": "src/app.js", "functionName": "parse" }` | Text: paste-ready `@nudo:case` directives when every case is call-site synthesized, e.g. `Function "parse" has 2 synthesized case(s); suggested directives:`; otherwise the current case count, e.g. `Function "parse" already has 3 case(s)`, or a suggested `@nudo:case` directive |
-| `nudo.selectCase` (`nudo/selectCase`) | `{ "file": "src/app.js", "functionName": "parse", "caseIndex": 1 }` | `{ "success": true }` — switches the active case (affects hover/diagnostics until changed back) |
-| `nudo.getActiveCases` (`nudo/getActiveCases`) | `{ "file": "src/app.js" }` | `{ "parse": 1, "greet": 0 }` — active case index per function |
-
-Diagnostics (failed `@nudo:returns` assertions, unreachable code, …) are available as LSP diagnostics — push (`textDocument/publishDiagnostics`) and pull (`textDocument/diagnostic`).
-
-## What-if workflow
-
-The signature move: hypothesize a type for one binding, observe what another binding becomes — without editing any source.
-
-```js
-// src/app.js
-function normalize(x) {
-  const trimmed = x.trim();
-  const y = Number(trimmed);
-  return y;
-}
-```
-
-Assume `x` is a string, ask what `y` is:
-
-```json
-{
-  "command": "nudo.whatIf",
-  "arguments": [{
-    "file": "src/app.js",
-    "bindings": [{ "name": "x", "type": "string" }],
-    "target": "y"
-  }]
-}
-```
-
-→ `Type of "y": number`. Then flip the hypothesis (`"type": "string | null"`) and re-ask to see how the code's guard branches change the result. Use this to preview refactors, validate an API's return type before calling it, or check that a fix actually narrows a type.
-
-## Type expression syntax
-
-`bindings[].type` accepts a primitive or a `|`-separated union of primitives:
-
-- `number`, `string`, `boolean`, `null`, `undefined`, `bigint`, `symbol`
-- Unions: `string | null`, `number | string`
-
-## Notes
-
-- **Unopened files use disk state.** If the file is not open in a connected editor, analysis runs on the on-disk content; edits the user has not saved are invisible.
-- Commands that report types reflect Nudo's inference, which follows runtime semantics (e.g. `Number("")` is `0`, not an error) — trust them over guesswork, but remember they describe the current code, not the user's intent.
-- Whole-program inference means every function with inferable call sites already has cases. When all of them are call-site synthesized, `suggestCase` returns ready-to-paste `@nudo:case` directive text (paste it above the function); `already has N case(s)` (handwritten or entry-only cases) is the normal report for the rest, not an error.

package/src/__tests__/definition.test.ts

@@ -1,32 +0,0 @@
-import { describe, it, expect } from "vitest";
-import { parse } from "@nudojs/parser";
-import { buildSymbolTable, findDefinition, findReferences } from "../symbols.ts";
-
-describe("symbol table", () => {
-  it("finds function definition", () => {
-    const source = `function add(a, b) { return a + b; }`;
-    const ast = parse(source);
-    const table = buildSymbolTable(ast, "file:///test.js");
-    const def = findDefinition(table, "add");
-    expect(def).not.toBeNull();
-    expect(def!.kind).toBe("function");
-    expect(def!.loc.start.line).toBe(1);
-  });
-
-  it("finds variable definition", () => {
-    const source = `const x = 42;`;
-    const ast = parse(source);
-    const table = buildSymbolTable(ast, "file:///test.js");
-    const def = findDefinition(table, "x");
-    expect(def).not.toBeNull();
-    expect(def!.kind).toBe("variable");
-  });
-
-  it("collects references", () => {
-    const source = `const x = 42; const y = x + 1;`;
-    const ast = parse(source);
-    const table = buildSymbolTable(ast, "file:///test.js");
-    const refs = table.references.filter((r) => r.name === "x");
-    expect(refs.length).toBeGreaterThan(0);
-  });
-});