lim 0.32.1 → 0.32.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 +16 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -12,6 +12,22 @@ npm install -g lim
|
|
|
12
12
|
npx lim <command>
|
|
13
13
|
```
|
|
14
14
|
|
|
15
|
+
### DotSlash (standalone, no Node.js required)
|
|
16
|
+
|
|
17
|
+
Every `lim-v*` [GitHub release](https://github.com/limrun-inc/typescript-sdk/releases) includes a [DotSlash](https://dotslash-cli.com/) file named `lim`. It is a small text file you can commit to your repository; the first time it runs, DotSlash fetches, verifies, and caches a self-contained `lim` build (with a bundled Node.js runtime) for your platform. Linux, macOS, and Windows are supported, each on x86_64 and arm64.
|
|
18
|
+
|
|
19
|
+
With [`dotslash` on your `PATH`](https://dotslash-cli.com/docs/installation/), on macOS and Linux:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
curl -LOSf https://github.com/limrun-inc/typescript-sdk/releases/download/lim-v0.32.1/lim
|
|
23
|
+
chmod +x lim
|
|
24
|
+
./lim --version
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Windows does not use shebangs, so invoke the file through `dotslash` explicitly (`dotslash lim --version`) or create a sibling `lim.bat` containing `@dotslash.exe "%~dpn0" %*` as described in [DotSlash on Windows](https://dotslash-cli.com/docs/windows/).
|
|
28
|
+
|
|
29
|
+
The same releases also carry the underlying per-platform tarballs (e.g. `lim-v0.32.1-<sha>-darwin-arm64.tar.gz`) if you prefer to extract one manually and run `lim/bin/lim` (`lim\bin\lim.cmd` on Windows) directly.
|
|
30
|
+
|
|
15
31
|
### Migrating from `@limrun/cli`
|
|
16
32
|
|
|
17
33
|
`lim` is the canonical npm package for the Limrun CLI. If you already installed the older scoped package, remove it before installing `lim` so npm does not hit a global `lim` binary conflict:
|
package/package.json
CHANGED