v1.4.0

.smartconfig.json

@@ -0,0 +1,37 @@
+{
+  "@git.zone/cli": {
+    "projectType": "npm",
+    "module": {
+      "githost": "code.foss.global",
+      "gitscope": "push.rocks",
+      "gitrepo": "smartrust",
+      "description": "A type-safe bridge between JavaScript engines and Rust binaries.",
+      "npmPackagename": "@push.rocks/smartrust",
+      "license": "MIT",
+      "projectDomain": "push.rocks",
+      "keywords": [
+        "rust",
+        "typescript",
+        "ipc",
+        "bridge",
+        "stdio",
+        "socket",
+        "binary",
+        "transport"
+      ]
+    },
+    "release": {
+      "accessLevel": "public",
+      "registries": [
+        "https://verdaccio.lossless.digital",
+        "https://registry.npmjs.org"
+      ]
+    }
+  },
+  "@git.zone/tsdoc": {
+    "legal": "\n## License and Legal Information\n\nThis repository contains open-source code licensed under the MIT License. A copy of the license can be found in the [license](./license) file.\n\n**Please note:** The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.\n\n### Trademarks\n\nThis project is owned and maintained by Task Venture Capital GmbH. The names and logos associated with Task Venture Capital GmbH and any related products or services are trademarks of Task Venture Capital GmbH or third parties, and are not included within the scope of the MIT license granted herein.\n\nUse of these trademarks must comply with Task Venture Capital GmbH's Trademark Guidelines or the guidelines of the respective third-party owners, and any usage must be approved in writing. Third-party trademarks used herein are the property of their respective owners and used only in a descriptive manner, e.g. for an implementation of an API or similar.\n\n### Company Information\n\nTask Venture Capital GmbH\nRegistered at District Court Bremen HRB 35230 HB, Germany\n\nFor any legal inquiries or further information, please contact us via email at hello@task.vc.\n\nBy using this repository, you acknowledge that you have read this section, agree to comply with its terms, and understand that the licensing of the code does not imply endorsement by Task Venture Capital GmbH of any derivative works.\n"
+  },
+  "@ship.zone/szci": {
+    "npmGlobalTools": []
+  }
+}

changelog.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## 2026-04-30 - 1.4.0 - feat(package)
+improve package metadata and standardize project configuration
+
+- replace npmextra.json with .smartconfig.json and expand project metadata
+- add package publishing metadata including files, keywords, homepage, repository, bugs, and packageManager
+- tighten TypeScript configuration with noImplicitAny and explicit node types
+- update build tooling dependencies and remove the allowimplicitany build flag
+- add a license file and align readme references and install instructions
+
+## 2026-03-14 - 1.3.2 - fix(rustbinarylocator)
+support resolving platform-suffixed local Rust binaries
+
+- Checks local Rust build paths for binaries with platform suffixes such as _linux_amd64 in addition to unsuffixed names
+- Adds platform and architecture suffix mapping for linux, darwin, windows, x64, and arm64
+
+## 2026-02-26 - 1.3.1 - fix(readme)
+document socket transport and clarify stdio/socket differences in README
+
+- Add 'Two Transport Modes' section documenting stdio (spawn) and socket (connect) modes
+- Add examples for connect(), socket usage, and auto-reconnect with exponential backoff
+- Clarify protocol is transport-agnostic and update ready/stream/event descriptions
+- Update event docs: mark stderr as stdio-only and add 'reconnected' event for socket transports
+- Clarify kill() behavior for both stdio and socket transports
+- Add API reference entries for SocketTransport, StdioTransport, ISocketConnectOptions, IRustTransport, and LineScanner
+- Add platform notes, architecture diagram, and minimal Rust/socket usage guidance
+
 ## 2026-02-26 - 1.3.0 - feat(transport)
 introduce transport abstraction and socket-mode support for RustBridge
 

license

@@ -0,0 +1,19 @@
+Copyright (c) 2014 Task Venture Capital GmbH (hello@task.vc)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

npmextra.json

@@ -1,24 +0,0 @@
-{
-  "@git.zone/cli": {
-    "projectType": "npm",
-    "module": {
-      "githost": "code.foss.global",
-      "gitscope": "push.rocks",
-      "gitrepo": "smartrust",
-      "description": "a bridge between JS engines and rust",
-      "npmPackagename": "@push.rocks/smartrust",
-      "license": "MIT",
-      "projectDomain": "push.rocks"
-    },
-    "release": {
-      "accessLevel": "public",
-      "registries": [
-        "https://verdaccio.lossless.digital",
-        "https://registry.npmjs.org"
-      ]
-    }
-  },
-  "@ship.zone/szci": {
-    "npmGlobalTools": []
-  }
-}

package.json

@@ -1,8 +1,8 @@
 {
   "name": "@push.rocks/smartrust",
-  "version": "1.3.0",
+  "version": "1.4.0",
   "private": false,
-  "description": "a bridge between JS engines and rust",
+  "description": "A type-safe bridge between JavaScript engines and Rust binaries.",
   "main": "dist_ts/index.js",
   "typings": "dist_ts/index.d.ts",
   "type": "module",
@@ -10,16 +10,46 @@
   "license": "MIT",
   "scripts": {
     "test": "(tstest test/ --verbose --logfile --timeout 60)",
-    "build": "(tsbuild tsfolders --allowimplicitany)",
+    "build": "(tsbuild tsfolders)",
     "buildDocs": "(tsdoc)"
   },
   "devDependencies": {
-    "@git.zone/tsbuild": "^4.1.2",
+    "@git.zone/tsbuild": "^4.4.0",
-    "@git.zone/tsrun": "^2.0.1",
+    "@git.zone/tsrun": "^2.0.2",
-    "@git.zone/tstest": "^3.1.8",
+    "@git.zone/tstest": "^3.6.3",
-    "@types/node": "^25.2.0"
+    "@types/node": "^25.6.0"
   },
   "dependencies": {
     "@push.rocks/smartpath": "^6.0.0"
-  }
+  },
+  "files": [
+    "ts/**/*",
+    "dist/**/*",
+    "dist_*/**/*",
+    "dist_ts/**/*",
+    "assets/**/*",
+    "cli.js",
+    ".smartconfig.json",
+    "license",
+    "readme.md"
+  ],
+  "keywords": [
+    "rust",
+    "typescript",
+    "ipc",
+    "bridge",
+    "stdio",
+    "socket",
+    "binary",
+    "transport"
+  ],
+  "homepage": "https://code.foss.global/push.rocks/smartrust#readme",
+  "repository": {
+    "type": "git",
+    "url": "https://code.foss.global/push.rocks/smartrust.git"
+  },
+  "bugs": {
+    "url": "https://code.foss.global/push.rocks/smartrust/issues"
+  },
+  "packageManager": "pnpm@10.28.2"
 }

readme.md

@@ -1,6 +1,6 @@
 # @push.rocks/smartrust
 
-A type-safe, production-ready bridge between TypeScript and Rust binaries via JSON-over-stdin/stdout IPC — with support for request/response, streaming, and event patterns.
+A type-safe, production-ready bridge between TypeScript and Rust binaries — with support for **stdio** (child process) and **socket** (Unix socket / Windows named pipe) transports, request/response, streaming, and event patterns.
 
 ## Issue Reporting and Security
 
@@ -9,32 +9,39 @@ For reporting bugs, issues, or security vulnerabilities, please visit [community
 ## Install 📦
 
 ```bash
-npm install @push.rocks/smartrust
+pnpm add @push.rocks/smartrust
-# or
-pnpm install @push.rocks/smartrust
 ```
 
 ## Overview 🔭
 
-`@push.rocks/smartrust` provides a complete bridge for TypeScript applications that need to communicate with Rust binaries. It handles the entire lifecycle — binary discovery, process spawning, request/response correlation, **streaming responses**, event pub/sub, and graceful shutdown — so you can focus on your command definitions instead of IPC plumbing.
+`@push.rocks/smartrust` provides a complete bridge for TypeScript applications that need to communicate with Rust binaries. It handles the entire lifecycle — binary discovery, process spawning **or socket connection**, request/response correlation, **streaming responses**, event pub/sub, and graceful shutdown — so you can focus on your command definitions instead of IPC plumbing.
+
+### Two Transport Modes 🔌
+
+| Mode | Method | Use Case |
+|------|--------|----------|
+| **Stdio** | `bridge.spawn()` | Spawn the Rust binary as a child process. Communicate via stdin/stdout. |
+| **Socket** | `bridge.connect(path)` | Connect to an **already-running** Rust daemon via Unix socket or Windows named pipe. |
+
+The JSON protocol is identical in both modes — only the transport layer changes. Socket mode enables use cases where the Rust binary runs as a **privileged system service** (e.g., a VPN daemon needing root for TUN devices, a network proxy binding to privileged ports) while the TypeScript app connects to it unprivileged.
 
 ### Why? 🤔
 
 If you're integrating Rust into a Node.js project, you'll inevitably need:
 - A way to **find** the compiled Rust binary across different environments (dev, CI, production, platform packages)
-- A way to **spawn** it and establish reliable two-way communication
+- A way to **spawn it** or **connect to it** and establish reliable two-way communication
 - **Type-safe** request/response patterns with proper error handling
 - **Streaming responses** for progressive data processing, log tailing, or chunked transfers
 - **Event streaming** from Rust to TypeScript
-- **Graceful lifecycle management** (ready detection, clean shutdown, force kill)
+- **Graceful lifecycle management** (ready detection, clean shutdown, auto-reconnection)
 
-`smartrust` wraps all of this into three classes: `RustBridge`, `RustBinaryLocator`, and `StreamingResponse`.
+`smartrust` wraps all of this into a clean API: `RustBridge`, `RustBinaryLocator`, `StreamingResponse`, and pluggable transports.
 
 ## Usage 🚀
 
 ### The IPC Protocol
 
-`smartrust` uses a simple, newline-delimited JSON protocol over stdin/stdout:
+`smartrust` uses a simple, newline-delimited JSON protocol:
 
 | Direction | Format | Description |
 |-----------|--------|-------------|
@@ -44,7 +51,7 @@ If you're integrating Rust into a Node.js project, you'll inevitably need:
 | **Rust → TS** (Stream Chunk) | `{"id": "req_1", "stream": true, "data": {...}}` | Intermediate chunk (zero or more) |
 | **Rust → TS** (Event) | `{"event": "ready", "data": {...}}` | Unsolicited event (no ID) |
 
-Your Rust binary reads JSON lines from stdin and writes JSON lines to stdout. That's it. Stderr is free for logging.
+This protocol works identically over stdio and socket transports. Your Rust binary reads JSON lines from one end and writes JSON lines to the other. That's it.
 
 ### Defining Your Commands
 
@@ -62,7 +69,9 @@ type TMyCommands = {
 };
 ```
 
-### Creating and Using the Bridge
+### Stdio Mode — Spawn a Child Process
+
+This is the classic mode. The bridge spawns the Rust binary and communicates via stdin/stdout:
 
 ```typescript
 const bridge = new RustBridge<TMyCommands>({
@@ -90,10 +99,62 @@ bridge.on('management:configChanged', (data) => {
   console.log('Config was changed:', data);
 });
 
-// Clean shutdown
+// Clean shutdown (SIGTERM → SIGKILL after 5s)
 bridge.kill();
 ```
 
+### Socket Mode — Connect to a Running Daemon 🔗
+
+When the Rust binary runs as a system service (e.g., via `systemd`, `launchd`, or a Windows Service), use `connect()` to talk to it over a Unix socket or named pipe:
+
+```typescript
+const bridge = new RustBridge<TMyCommands>({
+  binaryName: 'my-daemon',  // used for logging / error messages
+});
+
+// Connect to the daemon's management socket
+const ok = await bridge.connect('/var/run/my-daemon.sock');
+if (!ok) {
+  console.error('Failed to connect to daemon');
+  process.exit(1);
+}
+
+// Same API as stdio mode — completely transparent!
+const { pid } = await bridge.sendCommand('start', { port: 8080, host: '0.0.0.0' });
+const metrics = await bridge.sendCommand('getMetrics', {});
+
+// kill() closes the socket — it does NOT kill the daemon
+bridge.kill();
+```
+
+#### Auto-Reconnect
+
+For long-running applications, enable automatic reconnection with exponential backoff:
+
+```typescript
+const ok = await bridge.connect('/var/run/my-daemon.sock', {
+  autoReconnect: true,          // reconnect on unexpected disconnect
+  reconnectBaseDelayMs: 100,    // initial retry delay (doubles each attempt)
+  reconnectMaxDelayMs: 30000,   // max retry delay cap
+  maxReconnectAttempts: 10,     // give up after 10 attempts
+});
+
+// Listen for reconnection events
+bridge.on('reconnected', () => {
+  console.log('Reconnected to daemon!');
+});
+```
+
+#### Platform Notes
+
+| Platform | Socket Path Format | Example |
+|----------|-------------------|---------|
+| **Linux** | `/var/run/<name>.sock` or `$XDG_RUNTIME_DIR/<name>.sock` | `/var/run/my-daemon.sock` |
+| **macOS** | `/var/run/<name>.sock` | `/var/run/my-daemon.sock` |
+| **Windows** | `\\.\pipe\<name>` | `\\.\pipe\my-daemon` |
+
+Node.js `net.connect()` handles all formats transparently — no platform-specific code needed.
+
 ### Streaming Commands 🌊
 
 For commands where the Rust binary sends a series of chunks before a final result, use `sendCommandStreaming`. This is perfect for progressive data processing, log tailing, search results, or any scenario where you want incremental output.
@@ -231,6 +292,17 @@ const bridge = new RustBridge<TMyCommands>({
 });
 ```
 
+Socket connection options (passed to `bridge.connect()`):
+
+```typescript
+interface ISocketConnectOptions {
+  autoReconnect?: boolean;         // default: false
+  reconnectBaseDelayMs?: number;   // default: 100
+  reconnectMaxDelayMs?: number;    // default: 30000
+  maxReconnectAttempts?: number;   // default: 10
+}
+```
+
 ### Events 📡
 
 `RustBridge` extends `EventEmitter` and emits the following events:
@@ -238,8 +310,9 @@ const bridge = new RustBridge<TMyCommands>({
 | Event | Payload | Description |
 |-------|---------|-------------|
 | `ready` | — | Bridge connected and binary reported ready |
-| `exit` | `(code, signal)` | Rust process exited |
+| `exit` | `(code, signal)` | Transport closed (process exited or socket disconnected) |
-| `stderr` | `string` | A line from the binary's stderr |
+| `stderr` | `string` | A line from the binary's stderr (stdio mode only) |
+| `reconnected` | — | Socket transport reconnected after unexpected disconnect |
 | `management:<name>` | `any` | Custom event from Rust (e.g. `management:configChanged`) |
 
 ### Custom Logger 📝
@@ -263,7 +336,9 @@ const bridge = new RustBridge<TMyCommands>({
 
 ### Writing the Rust Side 🦀
 
-Your Rust binary needs to implement a simple protocol:
+Your Rust binary needs to implement a simple protocol. The transport (stdio or socket) doesn't change the message format — only how connections are established.
+
+#### Stdio Mode (Child Process)
 
 1. **On startup**, write a ready event to stdout:
    ```
@@ -280,7 +355,14 @@ Your Rust binary needs to implement a simple protocol:
 
 6. **Use stderr** for logging — it won't interfere with the IPC protocol
 
-Here's a minimal Rust skeleton:
+#### Socket Mode (Daemon)
+
+1. **Listen** on a Unix socket (e.g., `/var/run/my-daemon.sock`) or Windows named pipe
+2. **On each new client connection**, send the `{"event":"ready","data":{...}}\n` event
+3. Read/write JSON lines on the socket (same protocol as stdio)
+4. Support multiple concurrent clients — each connection is independent
+
+Here's a minimal Rust skeleton (stdio mode):
 
 ```rust
 use serde::{Deserialize, Serialize};
@@ -368,6 +450,33 @@ fn main() {
 }
 ```
 
+## Architecture 🏗️
+
+```
+┌──────────────────────────────────────────────────────┐
+│                    RustBridge<T>                      │
+│  (protocol layer: handleLine, sendCommand, events)   │
+├──────────────┬───────────────────────────────────────┤
+│ StdioTransport │         SocketTransport             │
+│  spawn() +     │   net.connect() + auto-reconnect    │
+│  stdin/stdout  │   Unix socket / named pipe          │
+├──────────────┴───────────────────────────────────────┤
+│               IRustTransport interface               │
+│         connect() / write() / disconnect()           │
+├──────────────────────────────────────────────────────┤
+│       LineScanner (shared newline scanner)            │
+├──────────────────────────────────────────────────────┤
+│              RustBinaryLocator                        │
+│  (binary search — stdio mode only)                   │
+└──────────────────────────────────────────────────────┘
+```
+
+- **`RustBridge`** — The main class. Protocol-level logic (JSON parsing, request correlation, streaming, events) is transport-agnostic.
+- **`StdioTransport`** — Spawns a child process, manages stdin/stdout/stderr, handles SIGTERM/SIGKILL.
+- **`SocketTransport`** — Connects to an existing Unix socket or named pipe, with optional auto-reconnect and exponential backoff.
+- **`LineScanner`** — Shared buffer-based newline scanner used by both transports for efficient message framing.
+- **`RustBinaryLocator`** — Priority-ordered binary search (used by stdio mode only).
+
 ## API Reference 📖
 
 ### `RustBridge<TCommands>`
@@ -375,11 +484,12 @@ fn main() {
 | Method / Property | Signature | Description |
 |---|---|---|
 | `constructor` | `new RustBridge<T>(options: IRustBridgeOptions)` | Create a new bridge instance |
-| `spawn()` | `Promise<boolean>` | Spawn the binary and wait for ready; returns `false` on failure |
+| `spawn()` | `Promise<boolean>` | **Stdio mode**: Spawn the binary and wait for ready; returns `false` on failure |
+| `connect(socketPath, options?)` | `Promise<boolean>` | **Socket mode**: Connect to a running daemon; returns `false` on failure |
 | `sendCommand(method, params)` | `Promise<TCommands[K]['result']>` | Send a typed command and await the response |
 | `sendCommandStreaming(method, params)` | `StreamingResponse<TChunk, TResult>` | Send a streaming command; returns immediately |
-| `kill()` | `void` | SIGTERM the process, reject pending requests, force SIGKILL after 5s |
+| `kill()` | `void` | Stdio: SIGTERM the process, SIGKILL after 5s. Socket: close the connection (daemon stays alive) |
-| `running` | `boolean` | Whether the bridge is currently connected |
+| `running` | `boolean` | Whether the bridge is currently connected and ready |
 
 ### `StreamingResponse<TChunk, TResult>`
 
@@ -396,13 +506,43 @@ fn main() {
 | `findBinary()` | `Promise<string \| null>` | Find the binary using the priority search; result is cached |
 | `clearCache()` | `void` | Clear the cached path to force a fresh search |
 
+### `StdioTransport`
+
+| Method / Property | Signature | Description |
+|---|---|---|
+| `constructor` | `new StdioTransport(options: IStdioTransportOptions)` | Create a stdio transport |
+| `connect()` | `Promise<void>` | Spawn the child process |
+| `write(data)` | `Promise<void>` | Write to stdin with backpressure handling |
+| `disconnect()` | `void` | Kill the process (SIGTERM → SIGKILL after 5s) |
+| `connected` | `boolean` | Whether the process is running |
+
+### `SocketTransport`
+
+| Method / Property | Signature | Description |
+|---|---|---|
+| `constructor` | `new SocketTransport(options: ISocketTransportOptions)` | Create a socket transport |
+| `connect()` | `Promise<void>` | Connect to the Unix socket / named pipe |
+| `write(data)` | `Promise<void>` | Write to socket with backpressure handling |
+| `disconnect()` | `void` | Close the socket (does not kill the daemon) |
+| `connected` | `boolean` | Whether the socket is connected |
+
+### `LineScanner`
+
+| Method / Property | Signature | Description |
+|---|---|---|
+| `constructor` | `new LineScanner(maxPayloadSize, logger)` | Create a line scanner |
+| `push(chunk, onLine)` | `void` | Feed a `Buffer` chunk; calls `onLine` for each complete line |
+| `clear()` | `void` | Reset the internal buffer |
+
 ### Exported Interfaces & Types
 
 | Interface / Type | Description |
 |---|---|
 | `IRustBridgeOptions` | Full configuration for `RustBridge` |
 | `IBinaryLocatorOptions` | Configuration for `RustBinaryLocator` |
+| `ISocketConnectOptions` | Socket connection options (reconnect settings) |
 | `IRustBridgeLogger` | Logger interface: `{ log(level, message, data?) }` |
+| `IRustTransport` | Transport interface (extends `EventEmitter`) |
 | `IManagementRequest` | IPC request shape: `{ id, method, params }` |
 | `IManagementResponse` | IPC response shape: `{ id, success, result?, error? }` |
 | `IManagementEvent` | IPC event shape: `{ event, data }` |
@@ -414,7 +554,7 @@ fn main() {
 
 ## License and Legal Information
 
-This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the [LICENSE](./LICENSE) file.
+This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the [license](./license) file.
 
 **Please note:** The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.
 

ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@push.rocks/smartrust',
-  version: '1.3.0',
+  version: '1.4.0',
-  description: 'a bridge between JS engines and rust'
+  description: 'A type-safe bridge between JavaScript engines and Rust binaries.'
 }

ts/classes.rustbinarylocator.ts

@@ -81,11 +81,18 @@ export class RustBinaryLocator {
       plugins.path.resolve(process.cwd(), `rust/target/release/${binaryName}`),
       plugins.path.resolve(process.cwd(), `rust/target/debug/${binaryName}`),
     ];
+    const platformSuffix = this.getPlatformSuffix();
     for (const localPath of localPaths) {
       if (await this.isExecutable(localPath)) {
         this.logger.log('info', `Binary found at local path: ${localPath}`);
         return localPath;
       }
+      // Also try with platform suffix (tsrust convention: binaryName_linux_amd64)
+      const suffixedPath = `${localPath}_${platformSuffix}`;
+      if (await this.isExecutable(suffixedPath)) {
+        this.logger.log('info', `Binary found at local path (platform-suffixed): ${suffixedPath}`);
+        return suffixedPath;
+      }
     }
 
     // 5. System PATH
@@ -137,6 +144,14 @@ export class RustBinaryLocator {
     }
   }
 
+  private getPlatformSuffix(): string {
+    const archMap: Record<string, string> = { x64: 'amd64', arm64: 'arm64' };
+    const platformMap: Record<string, string> = { linux: 'linux', darwin: 'darwin', win32: 'windows' };
+    const platform = platformMap[process.platform] || process.platform;
+    const arch = archMap[process.arch] || process.arch;
+    return `${platform}_${arch}`;
+  }
+
   private async findInPath(binaryName: string): Promise<string | null> {
     const pathDirs = (process.env.PATH || '').split(plugins.path.delimiter);
     for (const dir of pathDirs) {

tsconfig.json

@@ -4,7 +4,11 @@
     "module": "NodeNext",
     "moduleResolution": "NodeNext",
     "esModuleInterop": true,
-    "verbatimModuleSyntax": true
+    "verbatimModuleSyntax": true,
+    "noImplicitAny": true,
+    "types": [
+      "node"
+    ]
   },
   "exclude": [
     "dist_*/**/*.d.ts"