@hydranium/langium 1.0.0-next.224 → 1.0.0-next.225

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.
Files changed (2) hide show
  1. package/README.md +8 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -11,12 +11,14 @@ project stays in lockstep with the version the framework was built against.
11
11
  ## Why this package exists
12
12
 
13
13
  Langium is pinned to **one exact version** here, to guarantee a **single physical copy** across the
14
- workspace. Re-export is transparent — given one physical install, importing `AstNode` or `URI` from
15
- `@hydranium/langium` and from `langium` yields the same class object and the same declaration. That
16
- transparency is exactly what a split install destroys: two copies of Langium mean two `AstNode`
17
- declarations and two `URI` classes, so `instanceof` and every nominal identity check across them
18
- silently start returning `false`. Without the pin, single-copy is only a semver-dedup coincidence,
19
- one minor bump away from breaking.
14
+ workspace. Re-export is transparent — given one physical install, importing `AstUtils` or
15
+ `OperationCancelled` from `@hydranium/langium` and from `langium` yields the same object and the
16
+ same declaration. That transparency is exactly what a split install destroys: two copies of Langium
17
+ mean two sets of declarations, which TypeScript refuses to mix, and two sets of module-level values,
18
+ so one that Langium compares by identity, such as its cancellation signal, is not recognised by the
19
+ other copy. The framework refuses to start a server whose AST reflection is built on a copy other
20
+ than its own. Without the pin, single-copy is only a semver-dedup coincidence, one minor bump away
21
+ from breaking.
20
22
 
21
23
  For an **adopter**, the reason to route imports here is not runtime identity (that already holds) —
22
24
  it is **version coupling**. Langium sits in a chain with `vscode-languageserver`,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hydranium/langium",
3
- "version": "1.0.0-next.224",
3
+ "version": "1.0.0-next.225",
4
4
  "description": "Augmented re-export of the Langium API for the hydranium framework: the single chokepoint where hydranium pins the Langium version and layers its type/namespace augmentations. ~99% passthrough today.",
5
5
  "keywords": [
6
6
  "hydranium",