@hamedb89/localghost 0.2.0 → 0.4.0

package/docs/flows.md

@@ -17,6 +17,15 @@ Choose the install command for the repository's package manager. Then initialize
 localghost init --write-scripts
 ```
 
+For a repository without Localghost installed, use the package-manager launcher first:
+
+```sh
+npm exec --yes --package=@hamedb89/localghost -- localghost init --write-scripts
+pnpm dlx @hamedb89/localghost init --write-scripts
+yarn dlx @hamedb89/localghost init --write-scripts
+bunx --package @hamedb89/localghost localghost init --write-scripts
+```
+
 ## Project Contract
 
 As a developer, I want one small file that explains the local domain map for this repo.
@@ -51,6 +60,8 @@ LOCALGHOST_NO_UPDATE_CHECK=1 localghost doctor
 
 Localghost checks npm after successful commands, caches the result for 24 hours, and ignores check failures. `LOCALGHOST_NO_UPDATE_CHECK=1` and `--no-update-check` disable the automatic check.
 
+To install or update the package in the current repository, run `localghost upgrade`. If no local CLI exists yet, invoke it through the package manager, for example `npm exec --yes --package=@hamedb89/localghost -- localghost upgrade`.
+
 ## One-Time Setup
 
 As a developer, I want one explicit setup command that updates only the managed Localghost block in `/etc/hosts` and validates Caddy.

package/docs/github.md

@@ -115,12 +115,12 @@ https://hamedb89.github.io/localghost/
 `.github/workflows/ci.yml` runs on pull requests and pushes to `main`. It uses `npm ci`, then runs:
 
 ```sh
-npm run release:check
+./bin/ghost check
 ```
 
-That command typechecks, builds the package, builds the static site, and runs `npm pack --dry-run`.
+That command typechecks, builds the package, builds the static site, and runs `npm pack --dry-run`. From a checkout, the same verification is available as `./bin/ghost check`.
 
-`.github/workflows/publish-npm.yml` publishes to npm when a `v*` tag is pushed, or from manual workflow dispatch. The workflow checks that tag names match `package.json` versions, reruns `npm run release:check`, and then uses:
+`.github/workflows/publish-npm.yml` publishes to npm when a `v*` tag is pushed, or from manual workflow dispatch. The workflow checks that tag names match `package.json` versions, reruns `./bin/ghost check`, and then uses:
 
 ```sh
 npm run publish:public
@@ -153,12 +153,12 @@ For a normal patch release:
 
 ```sh
 git status --short
-npm run release:check
+./bin/ghost check
 npm version patch
 git push origin main --tags
 ```
 
-Pushing the `v*` tag starts the npm publish workflow automatically. The workflow reruns `npm run release:check` before publishing. Create the GitHub release afterwards if you want release notes on GitHub.
+Pushing the `v*` tag starts the npm publish workflow automatically. The workflow reruns `./bin/ghost check` before publishing. Create the GitHub release afterwards if you want release notes on GitHub.
 
 If publishing from a local terminal instead of GitHub Actions, omit provenance and provide the npm two-factor code:
 

package/docs/localghost.1.md

@@ -19,8 +19,9 @@ localghost status [--ready] [--json]
 localghost ps [--json]
 localghost guide [--agent] [--json]
 localghost tunnel [--cwd path] [--config file] [--config-pattern regex] [--ghost-config file] [--target-host host]
-localghost release <patch|minor|major>
+localghost release [patch|minor|major]
 localghost update [--json]
+localghost upgrade [--cwd path]
 localghost dev [--config file] [--config-pattern regex] [--https|--ssl] [--auto-repair yes|no] [--trust]
 localghost run [--config file] [--config-pattern regex] [--https|--ssl] [--auto-repair yes|no] [--trust] [--dynamic-port] -- command
 localghost print [--config file] [--config-pattern regex]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hamedb89/localghost",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Friendly local hostnames for app repos with .localghost, Caddy, /etc/hosts, and Vite.",
   "type": "module",
   "bin": {