claude-use 0.2.5 → 0.2.7

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
@@ -49,7 +49,7 @@ scoop bucket add claude-use https://github.com/ExaDev/scoop-claude-use
49
49
  scoop install claude-use
50
50
  ```
51
51
 
52
- Every channel installs `claude-use` alone — none of them install a `claude` command; `claude-use shim enable` is the one explicit action that does, on any of them. The GitHub Release binary, Homebrew, and Scoop all ship the self-contained Node SEA build (no Node.js installation required) — macOS arm64, both Linux architectures, and Windows x64 are all targets Node core itself tests and verifies `--build-sea` against upstream; macOS x64 is published best-effort, since Node core does not test or verify single-executable-application support on that target. npm ships the plain bundle, running under whatever Node ≥ 22.12 you already have.
52
+ Every channel installs `claude-use` alone — none of them install a `claude` command; `claude-use shim enable` is the one explicit action that does, on any of them. The GitHub Release binary, Homebrew, and Scoop all ship the self-contained Node SEA build (no Node.js installation required) — macOS arm64, both Linux architectures, and both Windows architectures are all targets Node core itself tests and verifies `--build-sea` against upstream; macOS x64 is published best-effort, since Node core does not test or verify single-executable-application support on that target. npm ships the plain bundle, running under whatever Node ≥ 22.12 you already have.
53
53
 
54
54
  ## Quick start
55
55
 
@@ -525,7 +525,7 @@ The reverse direction matters just as much: a directory materialised because of
525
525
 
526
526
  One gotcha worth knowing before reaching for this: **Homebrew's macOS Node build has the single-executable-application feature compiled out.** Running the build against a Homebrew-installed Node fails partway through with "Single executable application is disabled" — `scripts/build.mts` detects this specific error and rewrites it into an explanation naming the cause, rather than leaving a contributor to debug an opaque native error. Use a Node binary from a distribution that ships SEA support instead — the official nodejs.org build, or a version manager installing upstream builds (mise, nvm, volta, fnm) — ahead of Homebrew's on `PATH`.
527
527
 
528
- macOS SEA support is tested and verified upstream on **arm64 only** — x64 is explicitly unsupported and skipped in Node core's own test suite. CI builds and publishes the arm64 binary as the verified release artefact; it also attempts an x64 build as a clearly-labelled best-effort convenience (allowed to fail without blocking the release, and published as `claude-use-macos-x64-unverified` when it succeeds), never presented as a supported target.
528
+ macOS SEA support is tested and verified upstream on **arm64 only** — x64 is explicitly unsupported and skipped in Node core's own test suite. CI builds and publishes the arm64 binary as the verified release artefact; it also attempts an x64 build as a clearly-labelled best-effort convenience (allowed to fail without blocking the release, and published as `claude-use-macos-x64-unverified` when it succeeds), never presented as a supported target. Windows and Linux carry no such carve-out — Node's own SEA documentation tests both regularly across every architecture it supports on those platforms (x64 and arm64 alike), so CI builds and verifies all four of those binaries as fully supported release artefacts, same as macOS arm64.
529
529
 
530
530
  ### Publishing to npm
531
531
 
package/dist/cli.cjs CHANGED
@@ -221857,7 +221857,7 @@ var categories_default_default = {
221857
221857
  // package.json
221858
221858
  var package_default = {
221859
221859
  name: "claude-use",
221860
- version: "0.2.5",
221860
+ version: "0.2.7",
221861
221861
  description: "A profile manager and launcher for Claude Code that lets one person run multiple logins from one machine while controlling what gets shared between them.",
221862
221862
  license: "Apache-2.0",
221863
221863
  author: "Joseph Mearman <joseph@mearman.co.uk>",
@@ -240957,6 +240957,9 @@ var UnsupportedShimSourceError = class extends Error {
240957
240957
  function claudeTargetFilename(ownExecutablePath) {
240958
240958
  return ownExecutablePath.toLowerCase().endsWith(".exe") ? "claude.exe" : "claude";
240959
240959
  }
240960
+ function isInvokedAsClaude(invokedName) {
240961
+ return invokedName === "claude" || invokedName.toLowerCase() === "claude.exe";
240962
+ }
240960
240963
  function resolveOwnInstallDirs(paths, ownExecutablePath) {
240961
240964
  const dirs = [import_node_path17.default.dirname(ownExecutablePath)];
240962
240965
  const state = readJson(paths.claudeShimFile, ClaudeShimStateSchema);
@@ -241765,7 +241768,7 @@ function runClaude(argvOverride) {
241765
241768
  }
241766
241769
  function main() {
241767
241770
  const invokedName = import_node_path20.default.basename(process.argv[1] ?? "claude-use");
241768
- if (invokedName === "claude") {
241771
+ if (isInvokedAsClaude(invokedName)) {
241769
241772
  runClaude();
241770
241773
  } else {
241771
241774
  buildClaudeUseProgram().parse(process.argv);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-use",
3
- "version": "0.2.5",
3
+ "version": "0.2.7",
4
4
  "description": "A profile manager and launcher for Claude Code that lets one person run multiple logins from one machine while controlling what gets shared between them.",
5
5
  "license": "Apache-2.0",
6
6
  "author": "Joseph Mearman <joseph@mearman.co.uk>",