codeanalyzer-typescript 0.2.0__py3-none-win_amd64.whl → 0.2.1__py3-none-win_amd64.whl

codeanalyzer_typescript/__init__.py

@@ -18,7 +18,7 @@ import sys
 from importlib import resources
 from pathlib import Path
 
-__version__ = "0.2.0"
+__version__ = "0.2.1"
 
 __all__ = ["bin_path", "__version__"]
 

codeanalyzer_typescript/__main__.py

@@ -0,0 +1,34 @@
+"""Console-script entry point: run the bundled ``cants`` binary.
+
+``pip install codeanalyzer-typescript`` installs a ``cants`` launcher (see
+``[project.scripts]`` in ``pyproject.toml``) that calls :func:`main`. We locate
+the platform binary via :func:`bin_path` and hand off the process to it, passing
+through every CLI argument and the exit code unchanged.
+"""
+
+from __future__ import annotations
+
+import os
+import subprocess
+import sys
+
+from . import bin_path
+
+
+def main() -> "int | None":
+    """Exec the bundled ``cants`` binary with the current argv (minus argv[0])."""
+    binary = str(bin_path())
+    args = [binary, *sys.argv[1:]]
+
+    if os.name == "posix":
+        # Replace this process with the binary: no extra Python process lingers,
+        # and signals/exit codes are handled by cants directly.
+        os.execv(binary, args)
+        # os.execv never returns on success.
+
+    # Windows has no execv that behaves like POSIX; spawn and propagate the code.
+    return subprocess.call(args)
+
+
+if __name__ == "__main__":
+    sys.exit(main())

{codeanalyzer_typescript-0.2.0.dist-info → codeanalyzer_typescript-0.2.1.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codeanalyzer-typescript
-Version: 0.2.0
+Version: 0.2.1
 Summary: Prebuilt codeanalyzer-typescript backend binary for CLDK (codellm-devkit).
 Project-URL: Homepage, https://codellm-devkit.info
 Project-URL: Repository, https://github.com/codellm-devkit/codeanalyzer-ts
@@ -25,6 +25,16 @@ It is the TypeScript backend behind [CLDK](https://github.com/codellm-devkit/pyt
 mirroring its [Python](https://github.com/codellm-devkit/codeanalyzer-python) and
 [Java](https://github.com/codellm-devkit/codeanalyzer-java) siblings.
 
+## Install
+
+```bash
+pip install codeanalyzer-typescript
+```
+
+The wheel bundles a prebuilt, self-contained `cants` binary for your platform (no Bun or
+Node required to run it) and installs a `cants` command on your `PATH`. CLDK's Python SDK
+depends on this package to locate the analyzer backend.
+
 ## Usage
 
 The analyzer provides a command-line interface for performing static analysis on
@@ -51,8 +61,9 @@ Options:
   -o, --output <dir>             output directory for analysis.json
                                  (omit ⇒ compact JSON to stdout)
   -f, --format <fmt>             output format: json | msgpack (default: "json")
-  -a, --analysis-level <n>       1 = tsc resolver call graph + RTA (default);
-                                 2 = + CodeQL enrichment (default: "1")
+  -a, --analysis-level <n>       analysis depth: 1 = symbol table + tsc resolver
+                                 call graph + RTA (default); 2 = call graph
+                                 (default: "1")
   -t, --target-files <paths...>  restrict analysis to specific files (incremental)
       --skip-tests               skip test trees (default)
       --include-tests            include test trees
@@ -90,14 +101,14 @@ Options:
    This saves the results to `analysis.msgpack`, a binary format that is more compact for
    storage and transmission.
 
-3. **Deeper analysis with CodeQL enrichment (experimental):**
+3. **Selecting an analysis level:**
    ```bash
    cants --input ./my-ts-project --analysis-level 2
    ```
 
-   Every run produces a symbol table **and** a call graph. At level 1, edges come from the
-   TypeScript compiler's resolver plus Rapid Type Analysis (RTA), with phantom nodes for
-   calls into imported libraries. Level 2 additionally merges in CodeQL-derived edges.
+   Every run produces a symbol table **and** a call graph. Edges come from the TypeScript
+   compiler's resolver plus Rapid Type Analysis (RTA), with phantom nodes for calls into
+   imported libraries.
 
 4. **Incremental analysis of specific files:**
    ```bash

codeanalyzer_typescript-0.2.1.dist-info/RECORD

@@ -0,0 +1,8 @@
+codeanalyzer_typescript/__init__.py,sha256=Hw1tNYgyQ4tfINY8HBmrPfsjrD-440CFX9Kv5HmqktI,1836
+codeanalyzer_typescript/__main__.py,sha256=f8C3GgPB5RutSyYkwjas31c3M0zae5sKeudYWXHuQIg,1054
+codeanalyzer_typescript/_bin/.gitignore,sha256=_mZ_61eDWQ65V05VrmLP33rSeppQmwCwV8_qsgHUOHM,251
+codeanalyzer_typescript/_bin/cants.exe,sha256=uVoKpzAyRSHbVW0QPuiggxB7FrP9RYvHPGKlk_9f304,111491584
+codeanalyzer_typescript-0.2.1.dist-info/METADATA,sha256=2OkUhCjNpAXZF9Suikzix5fEwkbADkBkEwE-zQc-LUU,8779
+codeanalyzer_typescript-0.2.1.dist-info/WHEEL,sha256=pp_iTzO0EBcCvlZZV2dJYp6L2tdDWBsn1ceo50wEt8Q,94
+codeanalyzer_typescript-0.2.1.dist-info/entry_points.txt,sha256=-kWzUa53_kUEbiwup53Q5GqeSOdQM1iIRJHzPIwV7S0,64
+codeanalyzer_typescript-0.2.1.dist-info/RECORD,,

codeanalyzer_typescript-0.2.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+cants = codeanalyzer_typescript.__main__:main

codeanalyzer_typescript-0.2.0.dist-info/RECORD

@@ -1,6 +0,0 @@
-codeanalyzer_typescript/__init__.py,sha256=w_G2b2FETBJH7KqvG-e-kOMewShb69rc5--_B53A2ug,1836
-codeanalyzer_typescript/_bin/.gitignore,sha256=_mZ_61eDWQ65V05VrmLP33rSeppQmwCwV8_qsgHUOHM,251
-codeanalyzer_typescript/_bin/cants.exe,sha256=KTRR1UtbgwZmbhPWKga38qCfRjYxKlhT9835Mwnqf8c,111492608
-codeanalyzer_typescript-0.2.0.dist-info/METADATA,sha256=iiupqvPre6UG3Fz74gRdtPbUQtF-4soER-XX8cv2x5k,8518
-codeanalyzer_typescript-0.2.0.dist-info/WHEEL,sha256=pp_iTzO0EBcCvlZZV2dJYp6L2tdDWBsn1ceo50wEt8Q,94
-codeanalyzer_typescript-0.2.0.dist-info/RECORD,,