@cascode/cascode-cli 0.7.2 → 0.7.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,6 +8,14 @@ How it works
|
|
|
8
8
|
- On install, a small script downloads a prebuilt, self-contained `cascode` binary
|
|
9
9
|
for your OS/architecture from the GitHub Releases page.
|
|
10
10
|
- The `cascode` command is provided via the package `bin` and forwards args to the binary.
|
|
11
|
+
- Simulator dependencies are managed by the CLI. Install ngspice with:
|
|
12
|
+
|
|
13
|
+
cascode install ngspice
|
|
14
|
+
|
|
15
|
+
This default path downloads a prebuilt ngspice package from the same GitHub release tag as the
|
|
16
|
+
installed Cascode CLI version. To force source mode, run:
|
|
17
|
+
|
|
18
|
+
cascode install ngspice --from-source
|
|
11
19
|
|
|
12
20
|
Environment variables
|
|
13
21
|
- `CASCODE_DOWNLOAD_BASE` (optional): override the GitHub Releases base URL, e.g.
|
|
@@ -24,4 +32,3 @@ Notes
|
|
|
24
32
|
- Release artifacts are expected to be named `cascode-<rid>.<zip|tar.gz>`, where rid is one of:
|
|
25
33
|
`win-x64`, `win-arm64`, `osx-x64`, `osx-arm64`, `linux-x64`, `linux-arm64`.
|
|
26
34
|
- The repository’s release workflow should publish those assets alongside tags matching the npm package version.
|
|
27
|
-
|
package/package.json
CHANGED