@motionharness/cli 0.1.2 → 0.1.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/README.md CHANGED
@@ -1,6 +1,7 @@
1
1
  # MotionHarness CLI
2
2
 
3
- Install the CLI with npm on macOS Apple Silicon / arm64 or Windows 10/11 x64:
3
+ Install the CLI with npm on macOS (Apple Silicon or Intel), Windows 10/11 x64,
4
+ or Ubuntu 24.04 x64:
4
5
 
5
6
  Some versions are published for only one platform. Install a version that includes
6
7
  your platform; if `latest` omits it, select an older compatible version explicitly
@@ -19,18 +20,19 @@ Or run without a global installation:
19
20
  npx @motionharness/cli --help
20
21
  ```
21
22
 
22
- The CLI requires Node.js 22.15+. Projects that need dependencies installed also
23
+ The CLI requires Node.js 22.15+ (x64 Node.js on Intel Macs). Projects that need dependencies installed also
23
24
  require pnpm 10 or later. The CLI does not install or manage these tools. A new
24
25
  Pro project needs registry access to its matching `@motionharness/sdk` and other
25
26
  dependencies. Run `mh skill` for the authoring and Agent guide.
26
27
 
27
28
  Use `mh render ./clip.wav --project ./my-project` to export the audio mix, or
28
29
  `mh render ./frames.zip --project ./my-project` for a numbered PNG sequence.
29
- The CLI includes standalone LGPL FFmpeg and ffprobe, extracted automatically on
30
- first use; no separate FFmpeg installation or download is needed. Corresponding
30
+ The macOS and Windows packages include standalone LGPL FFmpeg and ffprobe,
31
+ extracted automatically on first use. Corresponding
31
32
  sources, licenses and the rebuild recipe are included under licenses/media in
32
- the runtime resource directory reported by mh doctor. MH_FFMPEG and MH_FFPROBE
33
- can select user-built replacements. PNG, APNG, PNG sequences and WAV use native
33
+ the runtime resource directory reported by mh doctor. On Ubuntu, install
34
+ the system tools with `sudo apt install ffmpeg`. ProRes requires FFmpeg 7+;
35
+ use `MH_FFMPEG` and `MH_FFPROBE` to select compatible alternatives. PNG, APNG, PNG sequences and WAV use native
34
36
  writers. Studio also offers MP4
35
37
  (H.264 or HEVC), ProRes MOV, GIF and WebP when the host supports the encoder.
36
38
 
@@ -42,17 +44,17 @@ platform trust or session-reload step reported by the command. Studio shows
42
44
  configuration status and an off switch; reinstalling preserves a previous opt-out.
43
45
 
44
46
  `@motionharness/cli` provides the `mh` command and selects an exactly matching
45
- platform package. `@motionharness/cli-darwin-arm64` contains `MotionHarness`;
47
+ platform package. `@motionharness/cli-darwin-arm64` and
48
+ `@motionharness/cli-darwin-x64` and `@motionharness/cli-linux-x64` contain `MotionHarness`;
46
49
  `@motionharness/cli-win32-x64` contains `MotionHarness.exe`. The native process uses
47
50
  this full product name; the command remains `mh`. Install the main package
48
- for the command. Windows ARM64, WSL and Linux packages are not provided; Linux
49
- can run from source. Keep optional dependencies enabled. Installation works with
51
+ for the command. The Linux package targets x64 with glibc. Keep optional dependencies enabled. Installation works with
50
52
  `--ignore-scripts`: there are no postinstall hooks or extra binary downloads.
51
53
 
52
54
  For installations predating this native filename, update with
53
55
  `npm install -g @motionharness/cli@latest --include=optional`.
54
56
 
55
- The npm command verifies the platform package and its version. On macOS it uses
57
+ The npm command verifies the platform package and its version. On macOS and Linux it uses
56
58
  experimental `process.execve()` to replace Node with Rust; unavailable API support
57
59
  produces an upgrade prompt. On Windows it starts and waits for `MotionHarness.exe`, preserving
58
60
  arguments, stdin/stdout/stderr and exit status.
@@ -85,13 +87,15 @@ viewing/interaction or Studio-specific diagnostics, preserving later user action
85
87
 
86
88
  The binary embeds MotionHarness's fixed runtime resources. On first use these expand into
87
89
  `~/Library/Caches/mh/runtime/<payload-sha256>/` on macOS or
88
- `%LOCALAPPDATA%\mh\cache\runtime\<payload-sha256>\` on Windows. Windows authentication
90
+ `%LOCALAPPDATA%\mh\cache-v2\runtime\<payload-sha256>\` on Windows. Windows authentication
89
91
  and daemon state use separate `auth` and `daemon` directories under `%LOCALAPPDATA%\mh`.
90
92
  These directories require current-user ownership and private ACLs, with no reparse
91
93
  points. `MH_CACHE_DIR` can select an
92
94
  absolute private writable base; `mh doctor` reports the resource location.
95
+ The new Windows default leaves the old `%LOCALAPPDATA%\mh\cache` in place, so a
96
+ cache created with the wrong owner by an earlier CLI does not block startup.
93
97
  A damaged cache is an error: stop processes using the affected hash, remove only
94
- that hash directory and retry. Older hashes are retained across upgrades.
98
+ that hash directory and retry. Older hashes in the active cache are retained across upgrades.
95
99
 
96
100
  Upgrade with `mh update` (or `npm install -g @motionharness/cli@latest`); uninstall with
97
101
  `npm uninstall -g @motionharness/cli`. Cached runtime resources remain on disk.
@@ -4,7 +4,12 @@ import { createRequire } from 'node:module';
4
4
  import { dirname, join, resolve } from 'node:path';
5
5
  import { fileURLToPath, pathToFileURL } from 'node:url';
6
6
 
7
- export const platforms = Object.freeze({ 'darwin-arm64': '@motionharness/cli-darwin-arm64', 'win32-x64': '@motionharness/cli-win32-x64' });
7
+ export const platforms = Object.freeze({
8
+ 'darwin-arm64': '@motionharness/cli-darwin-arm64',
9
+ 'darwin-x64': '@motionharness/cli-darwin-x64',
10
+ 'win32-x64': '@motionharness/cli-win32-x64',
11
+ 'linux-x64': '@motionharness/cli-linux-x64',
12
+ });
8
13
 
9
14
  export function resolveBinary(packageJson, platform = process.platform, arch = process.arch) {
10
15
  const entry = JSON.parse(readFileSync(packageJson, 'utf8'));
package/package.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "0.1.2",
2
+ "version": "0.1.4",
3
3
  "license": "UNLICENSED",
4
4
  "type": "module",
5
5
  "engines": {
@@ -16,15 +16,18 @@
16
16
  },
17
17
  "os": [
18
18
  "darwin",
19
- "win32"
19
+ "win32",
20
+ "linux"
20
21
  ],
21
22
  "cpu": [
22
23
  "arm64",
23
24
  "x64"
24
25
  ],
25
26
  "optionalDependencies": {
26
- "@motionharness/cli-darwin-arm64": "0.1.2",
27
- "@motionharness/cli-win32-x64": "0.1.2"
27
+ "@motionharness/cli-darwin-arm64": "0.1.4",
28
+ "@motionharness/cli-darwin-x64": "0.1.4",
29
+ "@motionharness/cli-win32-x64": "0.1.4",
30
+ "@motionharness/cli-linux-x64": "0.1.4"
28
31
  },
29
32
  "files": [
30
33
  "bin/mh",