lshed 0.7.2 → 0.7.4
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/CHANGELOG.md +20 -0
- package/README.md +14 -2
- package/dist/cli.js +256 -1807
- package/package.json +4 -5
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.7.4 — 2026-09-03
|
|
4
|
+
|
|
5
|
+
The first CI run on real macOS and Windows machines found three bugs. All of them were path comparisons that only hold on Linux.
|
|
6
|
+
|
|
7
|
+
- A stub whose symlink points into a package was not recognised as generated on **macOS or Windows**. The target of a broken link cannot be resolved, so it was compared unresolved: on macOS `/var/folders/...` never matches the package's real `/private/var/folders/...`. Paths are now resolved as far as they exist before being compared.
|
|
8
|
+
- The warning for a settings value pointing inside a package never fired on **Windows**, because it matched the raw path against JSON text where backslashes are escaped. It now walks the values and compares them as paths.
|
|
9
|
+
- Path comparison is one helper that strips the Windows `\\?\` prefix and ignores case there.
|
|
10
|
+
- The test that runs a package's `install:` script is skipped on Windows; `./setup` is a shell script and `cmd.exe` cannot run it.
|
|
11
|
+
|
|
12
|
+
## 0.7.3 — 2026-09-03
|
|
13
|
+
|
|
14
|
+
You no longer need Node to run lshed.
|
|
15
|
+
|
|
16
|
+
- **Standalone binaries** for Windows x64, macOS (arm64/x64) and Linux (x64/arm64), attached to every tagged release. They carry their own runtime (~60-85 MB) and need nothing installed. `npm run binaries` builds all five from one machine.
|
|
17
|
+
- **The npm package is self-contained.** `commander`, `yaml` and `zod` are bundled into `dist/cli.js` (627 KB) instead of being installed alongside it; `zod` alone was 7.9 MB. `npm install -g lshed` now downloads one file.
|
|
18
|
+
- The version is baked in at build time, so the binaries do not look for a `package.json` that is not there.
|
|
19
|
+
- The smoke script accepts `LSHED_CLI=<path>` and is run against the compiled binary in CI, so the binaries are tested, not just built.
|
|
20
|
+
|
|
21
|
+
The design assumed everyone using a coding agent already had Node, because Claude Code installs through npm. Claude Code also has a native installer, and that assumption cost a user their laptop.
|
|
22
|
+
|
|
3
23
|
## 0.7.2 — 2026-09-03
|
|
4
24
|
|
|
5
25
|
Joining a machine that already has a harness, found while preparing the Windows check.
|
package/README.md
CHANGED
|
@@ -25,11 +25,23 @@ Currently supports **Claude Code** (`~/.claude`). Other agents plug in through a
|
|
|
25
25
|
|
|
26
26
|
## Install
|
|
27
27
|
|
|
28
|
+
With Node 20 or newer:
|
|
29
|
+
|
|
28
30
|
```
|
|
29
|
-
npm install -g lshed
|
|
31
|
+
npm install -g lshed # or run it once: npx lshed status
|
|
30
32
|
```
|
|
31
33
|
|
|
32
|
-
Node
|
|
34
|
+
Without Node, download a standalone binary from the [latest release](https://github.com/LeeSongHeon-LSH/lshed/releases/latest) and put it on your PATH. It carries its own runtime, so it is ~80 MB.
|
|
35
|
+
|
|
36
|
+
| Platform | File |
|
|
37
|
+
|---|---|
|
|
38
|
+
| Windows x64 | `lshed-windows-x64.exe` → rename to `lshed.exe` |
|
|
39
|
+
| macOS Apple Silicon / Intel | `lshed-darwin-arm64` / `lshed-darwin-x64` |
|
|
40
|
+
| Linux x64 / arm64 | `lshed-linux-x64` / `lshed-linux-arm64` |
|
|
41
|
+
|
|
42
|
+
On macOS and Linux, `chmod +x` it first. The binaries are unsigned, so macOS warns on first run.
|
|
43
|
+
|
|
44
|
+
Either way you also need `git` on the PATH for packages and `sync`, and `claude` if your shed lists plugins.
|
|
33
45
|
|
|
34
46
|
## Quick start
|
|
35
47
|
|