@velarscript/node 0.10.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,148 @@
+# @velarscript/node
+
+The official Node.js runtime boundary for VelarScript. It owns the typed module
+contracts and implementations for `velar/fs`, `velar/env`, `velar/host`,
+`velar/serve`, `velar/path`, `velar/process`, `velar/terminal`,
+`velar/sqlite`, `velar/worker`, and `velar/websocket`, plus the Node target of
+`velar/http`.
+
+The API exposes VelarScript contracts rather than Node objects. Filesystem
+operations are bounded, process execution is shell-free and starts with a
+secret-minimizing environment, and HTTP streaming keeps timeout and
+cancellation active until the response body has finished. `secretHeader`
+references an environment variable without placing its value in VelarScript
+application state; creating a lazy request retains only its validated descriptor,
+the official runtime resolves the current value at the first effect and sends it
+only across the private host transport, and cross-origin redirects strip it.
+`HttpError`, `HttpAbortError`, and `HttpTransportError` separately represent
+non-2xx responses, owned cancel/deadline outcomes, and request/response network
+transport failure. The transport phase is typed; retry and replay policy stays
+with the provider or application.
+
+Started processes expose pull-based, enum-tagged stdout/stderr chunks through
+the ordinary VelarScript `async for` protocol. Each channel is decoded as one
+incremental UTF-8 stream; only one pull may be active, output is consumed before
+`wait`, and the same bounded aggregate remains available from `wait`.
+Process value validation and result assembly use one module-initialized host
+ABI shared with `@velarscript/desktop`. It captures the relevant JavaScript
+reflection, collection, Promise, timer, and immutable-result operations; both
+targets separately compose the compiler-owned captured UTF-8 runtime. Later
+prototype replacement therefore cannot redefine the official contract. This
+internal fragment is exported only from the compiler entry for target
+composition; it is not a public VelarScript module or an Agent abstraction.
+
+Node's actual child-process transport runs in one eagerly initialized Worker
+that imports only compiler-owned source and Node built-ins. This is necessary
+because Node's own spawn path dynamically consults public EventEmitter and
+stream prototypes; capturing only the wrapper methods in the application Realm
+would leave the official contract redirectable. The application-facing module uses a
+captured, bounded MessagePort protocol and revalidates every result. The Worker
+is unreferenced while idle, referenced while requests or children are active,
+and limits unreleased process handles to 128. None of Worker, MessagePort,
+ChildProcess, Buffer, or StringDecoder enters the VelarScript API.
+
+`velar/fs`, `velar/serve`, and the Node target of `velar/http` share a second isolated Worker through the private
+compiler dependency `velar/node-host-v1`. The name is an implementation edge,
+not an importable Standard API module. The application Realm validates paths,
+Velar values, handlers, runtime Types, strict JSON, UTF-8, and immutable result
+shapes. The Worker alone owns `node:fs/promises`, HTTP/HTTPS clients and servers,
+sockets, request/response streams, incremental fatal UTF-8 decoding, redirects,
+static-file reads, response writes, and backpressure. It imports only
+compiler-owned source and static Node built-ins; npm dependencies and
+VelarScript application code never execute in that Realm.
+
+The shared proxy eagerly completes one readiness handshake, caps pending
+operations at 1,024, and is unreferenced while idle. A pending filesystem,
+server, or HTTP operation and every active server or unread HTTP response retain
+the process. Server and request
+handles are bounded, wrap without colliding with live identities, and cap live
+servers at 128, inbound requests at 4,096, and outbound HTTP requests at 1,024.
+Every message is revalidated on both sides. In addition to each public request/file/stream limit, the Worker owns one
+128 MiB aggregate budget for cached request bodies, static files, buffered text
+responses, and in-flight stream chunks. A request returns its stable bytes only
+after the transport has finished or closed and all concurrent host operations
+have settled, preventing both leaks and disconnect-time double release.
+Filesystem creation uses one explicit no-clobber primitive: `createText(path,
+text)` reaches an OS exclusive-create operation in this Worker. It is never an
+existence check followed by `writeText`, so a concurrent creator or symbolic
+link cannot be overwritten between two host calls.
+Optimistic edits use `replaceTextIfMatches(path, expected, replacement)`. The
+Worker coordinates file mutations for one canonical target, compares exact
+UTF-8 bytes, and commits matching content with a same-directory rename. It
+returns `false` on a detected mismatch. This is atomic against cooperating
+operations inside the runtime host and never exposes a partial replacement,
+but it deliberately does not claim to lock unrelated processes that bypass the
+API.
+`watchFiles(path, recursive=false)` returns a resource-owned `FileWatcher`
+whose single active `next()` pull yields bounded, sorted, deduplicated absolute
+paths. A batch is an invalidation hint, not a lossless operating-system event
+log: an unknown filename or exhausted 4,096-path/2 MiB queue yields
+`{paths: [], rescan: true}`. At most 128 watchers are live; `close()` is
+idempotent, settles a pending pull with `null`, and releases the shared Worker
+reference. Native watcher failures are terminal. The returned path List is a
+validated ordinary VelarScript List rather than a frozen host collection.
+`velar/serve` keeps request and response JSON on the compiler-owned strict JSON
+boundary; its public runtime types and response dispatcher inspect own data
+descriptors without invoking getters or collection overrides.
+
+`velar/env` and `velar/host` each own a module-initialized host fragment rather
+than rediscovering application globals during an operation.
+Environment reads retain the original `process.env` identity and inspect only
+own data values. Graceful shutdown captures signal, exit, timer, Promise, and
+synchronous diagnostic operations. Filesystem validation captures path,
+number, decoder/encoder, typed-byte, reflection, and immutable-result
+operations; filesystem effects are delegated to the isolated shared Worker,
+so neither callback `node:fs` nor `node:fs/promises` is part of the
+application-Realm contract.
+
+Binary filesystem and HTTP operations use the target-neutral `Bytes` contract:
+`readBytes`, `writeBytes`, `createBytes`, Bytes request bodies, and response
+`.bytes()`. Node `Buffer` is confined to the isolated implementation and never
+becomes a VelarScript type or API.
+
+`velar/sqlite` owns a dedicated database Worker. It provides parameterized
+`execute`, runtime-Type checked `one`/`all`, prepared statements, bounded queues
+and results, `Bytes` BLOB values, and explicit transaction handles. Closing an
+uncommitted transaction rolls it back. Synchronous `node:sqlite` work never runs
+on the application thread.
+
+`velar/worker` resolves only entries declared in `velar.json`, validates each
+request and response, snapshots caller-owned transferable data, and transfers
+the snapshot's nested `Bytes`/fixed numeric buffers through a bounded cycle-safe
+data-graph scan without detaching the caller's values. It provides single-worker
+and bounded pool owners with per-call cancellation and timeout.
+`velar/websocket` provides pull connections bounded by both unread message count
+and aggregate bytes, preserves queued messages through normal EOF, and discards
+them on receive failure, plus a Node server; `listen({http: handler, ...})`
+serves the same typed HTTP contract as `velar/serve` on the upgrade port. Its
+only external transport dependency is the pinned `ws` package; native socket
+objects remain private.
+
+`velar/terminal` supplies bounded program arguments, backpressure-aware stdout
+and stderr writes, line input, interactive-terminal detection, and explicit
+reader cleanup. It lets a CLI remain pure VelarScript without exposing
+`process`, streams, readline events, or an unsafe JavaScript bridge. Closing the
+terminal is final even before the first read, and queued or oversized input is
+settled through `readLine` Promises rather than thrown from host event callbacks.
+The line decoder and fd writes belong to an eagerly initialized isolated
+Worker, but its stdin stream is created only by the first `readLine`; importing
+the module or writing output cannot make an otherwise idle CLI wait for input.
+On POSIX, the application-facing proxy duplicates stdin before dependencies
+run; `close()` either seals the never-opened reader or destroys the Worker's
+stream, waits for its closed handshake, and then closes that owned duplicate in
+the creating Realm. Idle imports and completed reads do not retain the CLI
+process.
+`velar/host` bounds both cleanup registration and the total graceful-shutdown
+window, so a stuck callback cannot indefinitely defeat SIGINT or SIGTERM.
+
+The compiler entry is independently reusable:
+
+```ts
+import { compile } from "@velarscript/compiler"
+import { velarNodeCompilerExtension } from "@velarscript/node/compiler"
+
+const result = compile(source, { extensions: [velarNodeCompilerExtension] })
+```
+
+`@velarscript/cli` composes this extension for local programs. Browser
+frameworks remain separate and reject Node-only modules before bundling.

package/dist/compiler.d.ts

@@ -0,0 +1,12 @@
+import { type CompilerExtension, type ModuleInterface } from "@velarscript/compiler";
+export { VELAR_PROCESS_HOST_RUNTIME } from "./process-runtime.ts";
+export declare const VELAR_NODE_API_VERSION = "0.10";
+export declare const VELAR_NODE_HOST_MODULE = "velar/node-host-v1";
+export declare const nodeModuleInterfaces: ReadonlyMap<string, ModuleInterface>;
+export declare const nodeModuleSources: ReadonlyMap<string, string>;
+export declare const nodeModuleDependencies: ReadonlyMap<string, readonly string[]>;
+export declare function isNodeModule(source: string): boolean;
+export declare function isNodeOnlyModule(source: string): boolean;
+export declare function nodeModuleDiagnostic(source: string): string;
+export declare const velarNodeCompilerExtension: CompilerExtension;
+//# sourceMappingURL=compiler.d.ts.map

package/dist/compiler.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"compiler.d.ts","sourceRoot":"","sources":["../src/compiler.ts"],"names":[],"mappings":"AAAA,OAAO,EAA0C,KAAK,iBAAiB,EAAiB,KAAK,eAAe,EAAkB,MAAM,uBAAuB,CAAC;AAiB5J,OAAO,EAAE,0BAA0B,EAAE,MAAM,sBAAsB,CAAC;AAElE,eAAO,MAAM,sBAAsB,SAAS,CAAC;AAC7C,eAAO,MAAM,sBAAsB,uBAAuB,CAAC;AAmR3D,eAAO,MAAM,oBAAoB,EAAE,WAAW,CAAC,MAAM,EAAE,eAAe,CAgJpE,CAAC;AAEH,eAAO,MAAM,iBAAiB,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CA0hBxD,CAAC;AAEH,eAAO,MAAM,sBAAsB,EAAE,WAAW,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,CASxE,CAAC;AAKH,wBAAgB,YAAY,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAEpD;AAED,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAExD;AAED,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAG3D;AAED,eAAO,MAAM,0BAA0B,EAAE,iBAUvC,CAAC"}