@tabnas/lsp 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -34,10 +34,13 @@ changes.
34
34
  ## Engine
35
35
 
36
36
  Requires a `@tabnas/parser` providing the LSP engine contract —
37
- recovery, `ruleDone` and `continuations`. The peer range is open by fleet
38
- convention, but the contract is newer than the current published engine;
39
- see `AGENTS.md` in the repository for the release constraint that
40
- applies before this package is published.
37
+ recovery, `ruleDone` and `continuations` which ships from **0.9.0**.
38
+
39
+ The peer range is deliberately open (`>=0`), the fleet convention, so an
40
+ install resolves the newest published engine. That is what satisfies the
41
+ contract in practice: install this package and npm gives you 0.9.0 or
42
+ later. Pinning an older engine by hand is the one way to get a resolution
43
+ that installs cleanly and then cannot serve — completion returns nothing.
41
44
 
42
45
  ## Documentation
43
46
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tabnas/lsp",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "type": "commonjs",
5
5
  "main": "src/core.js",
6
6
  "description": "Unified language server and language-server generator for tabnas grammars",
package/src/core.js CHANGED
@@ -11,7 +11,7 @@
11
11
  // the Go const in go/lsp.go (go/version_test.go): the release
12
12
  // orchestrator rewrites all three together, and the tests are what
13
13
  // turn a missed rewrite into a failure instead of a silent drift.
14
- const VERSION = '0.1.1'
14
+ const VERSION = '0.1.2'
15
15
 
16
16
  // Default engine-token -> LSP semantic-token-type map, sourced from
17
17
  // railroad's CANON key set (engine-standard tokens only; #ID is