@imfusion/web-ui 0.5.1-dev.30.gf9b152db → 0.5.1-dev.33.gadde98d1
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/package.json
CHANGED
|
@@ -1,9 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: imf-web-ui-update
|
|
3
3
|
description:
|
|
4
|
-
"Update @imfusion/web-ui in a consumer repository: refresh the package
|
|
5
|
-
|
|
6
|
-
separate approved commit."
|
|
4
|
+
"Update @imfusion/web-ui in a consumer repository: refresh the package, vendored skills, and lifecycle hooks, verify the
|
|
5
|
+
base update, then audit and optionally migrate affected or custom consumer components in a separate approved commit."
|
|
7
6
|
argument-hint: "[--dry-run] [optional version or reason]"
|
|
8
7
|
allowed-tools: Bash Read Grep
|
|
9
8
|
---
|
|
@@ -19,8 +18,7 @@ approval.
|
|
|
19
18
|
- Work from the frontend package root. In a monorepo, inspect package manifests and `git worktree list` first, then choose
|
|
20
19
|
the frontend package in the active worktree that uses web-ui. Read repository and component instructions before changing
|
|
21
20
|
files.
|
|
22
|
-
-
|
|
23
|
-
`yarn.lock`, and Bun for `bun.lock*`. If multiple lockfiles exist, stop and ask which is authoritative.
|
|
21
|
+
- This workflow uses npm. `package-lock.json` is the expected lockfile. Another lockfile is a conflict: stop and ask.
|
|
24
22
|
- A dry run is read-only. Do not install, run the installer, format, stage, commit, reset, or clean. Report what would run.
|
|
25
23
|
- Record the initial `git status --short`. Existing changes are held back, never staged or overwritten.
|
|
26
24
|
- A dirty file that the workflow needs to modify is a conflict. Stop and report it. This includes package files, installed
|
|
@@ -35,50 +33,37 @@ approval.
|
|
|
35
33
|
|
|
36
34
|
## Preflight
|
|
37
35
|
|
|
38
|
-
1. Select the frontend package in the active worktree and read its instructions, `package.json`, and
|
|
36
|
+
1. Select the frontend package in the active worktree and read its instructions, `package.json`, and `package-lock.json`.
|
|
39
37
|
2. Check whether `@imfusion/web-ui` is already declared and record its installed/version-marker version.
|
|
40
38
|
3. Record the worktree status and identify files the update would touch.
|
|
41
39
|
4. Inspect `.agents/skills/`, `.claude/skills/`, the `AGENTS.md` fence, `.claude/settings.json`, and `.agents/hooks/`.
|
|
42
|
-
5. Check for another
|
|
40
|
+
5. Check for another npm process. Stop on any conflict or ambiguous target.
|
|
43
41
|
|
|
44
42
|
## Base update
|
|
45
43
|
|
|
46
|
-
In a non-dry run, update the dependency
|
|
44
|
+
In a non-dry run, update the dependency:
|
|
47
45
|
|
|
48
46
|
```sh
|
|
49
47
|
npm install @imfusion/web-ui
|
|
50
48
|
```
|
|
51
49
|
|
|
52
|
-
|
|
53
|
-
|
|
50
|
+
Pass an explicit version only when the user supplied one. Do not use `--force` or `--legacy-peer-deps` to make installation
|
|
51
|
+
pass. Stop on install failure.
|
|
54
52
|
|
|
55
|
-
Then refresh the existing web-ui skill target:
|
|
53
|
+
Then refresh the existing web-ui skill target and lifecycle hooks:
|
|
56
54
|
|
|
57
55
|
```sh
|
|
58
56
|
npx web-ui-install --skills
|
|
57
|
+
npx web-ui-install --hooks
|
|
59
58
|
```
|
|
60
59
|
|
|
61
|
-
|
|
62
|
-
|
|
60
|
+
Run these from the consumer package root, the directory holding the `node_modules` that the dependency install just wrote.
|
|
61
|
+
`npx` resolves `web-ui-install` from the installed `@imfusion/web-ui` there; from any other directory it cannot find the
|
|
62
|
+
binary. Preserve the existing target (`.agents`, `.claude`, or both); do not silently choose a new one.
|
|
63
63
|
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
- If current web-ui hooks cover a responsibility, do not reinstall it.
|
|
69
|
-
- If no equivalent hook exists and the installer-owned destination is clean, ask whether to run:
|
|
70
|
-
|
|
71
|
-
```sh
|
|
72
|
-
npx web-ui-install --hooks
|
|
73
|
-
```
|
|
74
|
-
|
|
75
|
-
Run it only after the user accepts. Use the detected runner otherwise.
|
|
76
|
-
|
|
77
|
-
- If another hook covers a responsibility, do not stack a duplicate. Report the overlap and ask whether to leave hooks alone
|
|
78
|
-
or adapt the existing hook in a separate approved change.
|
|
79
|
-
- Invalid settings or dirty installer-owned hook files are conflicts. Stop and ask for resolution.
|
|
80
|
-
|
|
81
|
-
A declined hook offer is valid. Report `hooks: skipped by user` and continue.
|
|
64
|
+
Always run both installer commands after the package update. Skills and installer-owned hook scripts may have changed even
|
|
65
|
+
when their existing registrations already cover session start, prompt submit, and post-edit verification. The hook installer
|
|
66
|
+
refreshes those scripts wholesale and merges registrations idempotently. Stop on malformed settings or installer conflicts.
|
|
82
67
|
|
|
83
68
|
## Verification
|
|
84
69
|
|