@hydranium/langium 1.0.0-next.215 → 1.0.0-next.216

package/README.md

@@ -61,8 +61,8 @@ No peer dependencies: `langium` is a direct, exact dependency of this package.
 | `./node` | `langium/node` | `NodeFileSystem`.                         |
 | `./test` | `langium/test` | Parsing / validation test helpers.        |
 
-Each named subpath also resolves as `@hydranium/langium/lib/<name>`, so a consumer on classic
-`moduleResolution: "Node"` can reach it.
+Resolve the subpaths with [a resolver that reads `exports`](../../docs/adopting/requirements.md#a-resolver-that-reads-exports);
+`"Node"` (node10) reaches none of them.
 
 ## Usage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hydranium/langium",
-  "version": "1.0.0-next.215",
+  "version": "1.0.0-next.216",
   "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.",
   "keywords": [
     "hydranium",
@@ -42,25 +42,13 @@
       "types": "./lib/lsp.d.ts",
       "default": "./lib/lsp.js"
     },
-    "./lib/lsp": {
-      "types": "./lib/lsp.d.ts",
-      "default": "./lib/lsp.js"
-    },
     "./node": {
       "types": "./lib/node.d.ts",
       "default": "./lib/node.js"
     },
-    "./lib/node": {
-      "types": "./lib/node.d.ts",
-      "default": "./lib/node.js"
-    },
     "./test": {
       "types": "./lib/test.d.ts",
       "default": "./lib/test.js"
-    },
-    "./lib/test": {
-      "types": "./lib/test.d.ts",
-      "default": "./lib/test.js"
     }
   },
   "publishConfig": {