@tsonic/tsbindgen 0.7.20 → 0.7.22

package/README.md

@@ -78,6 +78,7 @@ npx tsbindgen generate -a ./MyLibrary.dll -d $DOTNET_RUNTIME -o ./my-lib --lib .
 | Command | Description |
 |---------|-------------|
 | `generate` | Generate TypeScript declarations from .NET assemblies |
+| `resolve-closure` | Resolve transitive assembly dependency closure (JSON) |
 
 ### Generate Options
 
@@ -85,6 +86,7 @@ npx tsbindgen generate -a ./MyLibrary.dll -d $DOTNET_RUNTIME -o ./my-lib --lib .
 |--------|-------|-------------|---------|
 | `--assembly` | `-a` | Path to assembly file(s) to process | - |
 | `--assembly-dir` | `-d` | Directory containing .NET runtime assemblies | - |
+| `--ref-dir` | - | Additional directory to search for referenced assemblies (repeatable) | - |
 | `--out-dir` | `-o` | Output directory for generated files | `out` |
 | `--namespaces` | `-n` | Namespace filter (reserved; currently ignored) | (all) |
 | `--naming` | - | Naming convention: `js` (camelCase) or `clr` (PascalCase) | `clr` |
@@ -95,12 +97,29 @@ npx tsbindgen generate -a ./MyLibrary.dll -d $DOTNET_RUNTIME -o ./my-lib --lib .
 | `--logs` | - | Enable specific log categories (repeatable; space-separated values) | - |
 | `--strict` | - | Enable strict mode validation | false |
 
+### resolve-closure
+
+Machine-readable dependency resolution for one or more seed assemblies. Useful for:
+- Debugging missing dependencies before generation
+- Tooling integrations (e.g. build systems) that need deterministic closure resolution
+
+```bash
+npx tsbindgen resolve-closure \
+  -a ./MyLibrary.dll \
+  --ref-dir $DOTNET_RUNTIME \
+  --ref-dir ./libs
+```
+
 ### Examples
 
 ```bash
 # Generate BCL with JavaScript naming
 npx tsbindgen generate -d $DOTNET_RUNTIME -o ./out --naming js
 
+# Generate a custom assembly when dependencies live outside the runtime directory
+npx tsbindgen generate -a ./MyLibrary.dll -d $DOTNET_RUNTIME -o ./out \
+  --ref-dir ./libs
+
 # Verbose output with specific log categories
 npx tsbindgen generate -d $DOTNET_RUNTIME -o ./out -v --logs ImportPlanner FacadeEmitter
 
@@ -132,6 +151,44 @@ output/
         └── metadata.json
 ```
 
+### Publishing Bindings Packages (dist/ + npm `exports`)
+
+When you publish bindings for your own assemblies (or generate them inside an npm workspace), you can keep generated artifacts out of git by writing them under `dist/` and exposing the facades via npm `exports`:
+
+```
+dist/tsonic/bindings/
+  Acme.Domain.js
+  Acme.Domain.d.ts
+  Acme.Domain/
+    bindings.json
+    internal/
+      index.d.ts
+      metadata.json
+```
+
+`package.json`:
+
+```json
+{
+  "type": "module",
+  "exports": {
+    "./package.json": "./package.json",
+    "./*.js": {
+      "types": "./dist/tsonic/bindings/*.d.ts",
+      "default": "./dist/tsonic/bindings/*.js"
+    }
+  }
+}
+```
+
+Consumers can then import CLR namespaces ergonomically:
+
+```ts
+import { TodoItem } from "@acme/domain/Acme.Domain.js";
+```
+
+Tsonic resolves the import using Node’s module resolution (including `exports`) and locates the nearest `bindings.json` for CLR discovery.
+
 ### Output Files
 
 | File | Description |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tsonic/tsbindgen",
-  "version": "0.7.20",
+  "version": "0.7.22",
   "description": "Generate TypeScript declarations from .NET assemblies",
   "type": "module",
   "bin": {