omakit 0.1.0 → 0.1.2

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.
Files changed (2) hide show
  1. package/README.md +6 -16
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -48,15 +48,6 @@ review writing. The rest of the benefit is the submitter's.
48
48
 
49
49
  ## Install
50
50
 
51
- On Omarchy, or any Arch:
52
-
53
- ```bash
54
- yay -S omakit
55
- omakit setup
56
- ```
57
-
58
- Anywhere with Node 22 or newer:
59
-
60
51
  ```bash
61
52
  npm install --global omakit
62
53
  omakit setup
@@ -72,15 +63,15 @@ omakit setup
72
63
 
73
64
  | Needs | Why |
74
65
  | --- | --- |
75
- | Node 22 or newer | the tool is plain ESM with no dependencies and no build step. A stock Omarchy has it through `mise`, along with `git`, `yay`, `gh` and `ttfx` |
66
+ | Node 22 or newer | the tool is plain ESM with no dependencies and no build step. A stock Omarchy has Node and npm through `mise`, along with `git`, `gh` and `ttfx` |
76
67
  | `git` | the pin, and reading a subject's tree at an exact commit |
77
68
  | network, once | `omakit pin`. After that, `submit` and `verify` on a local repository need none at all |
78
69
  | 15 MB on disk | the pinned checkout, in `$XDG_CACHE_HOME/omakit/marketplace`, or `~/.cache/omakit/marketplace` |
79
70
 
80
- Updates come from whichever installer you used: `omarchy-update` or `yay -Syu`
81
- for the package, `npm i -g omakit@latest` for npm, `omakit upgrade` for a
82
- clone. Nothing in omakit updates itself, and `omarchy-mise-install npm:omakit`
83
- would, so it is not the way in.
71
+ Updates come from whichever installer you used: `npm i -g omakit@latest` for
72
+ the package, `omakit upgrade` for a clone; `omakit doctor` says when a newer
73
+ version is published. Nothing in omakit updates itself, and
74
+ `omarchy-mise-install npm:omakit` would, so it is not the way in.
84
75
 
85
76
  ## Watch
86
77
 
@@ -178,8 +169,7 @@ and anything that is not a fast-forward, and it names what to run yourself in
178
169
  each case. It is not a self-updater of the kind this repository warns other
179
170
  people about: it fast-forwards a Git checkout you cloned, from the remote you
180
171
  cloned it from, and it touches nothing else. On a package install it says so and
181
- names the installer's own command: `npm i -g omakit@latest`, or
182
- `sudo pacman -Syu omakit` for the Arch package. `git -C ~/.local/share/omakit pull` still works
172
+ names the installer's own command, `npm i -g omakit@latest`. `git -C ~/.local/share/omakit pull` still works
183
173
  and does the same thing.
184
174
 
185
175
  **The pin** does not move by itself, ever, and `omakit upgrade` does not move it
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "omakit",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "The safe place to find out: everything knowable about an Omarchy Quattro plugin submission before you post it, on your own machine. Agent-first, read-only, posts nothing, zero dependencies.",
5
5
  "license": "MIT",
6
6
  "author": "Maarten Tolhuijs",