@spfx-fast/spfx-workbench 0.1.2 → 0.1.3

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 +2 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -31,7 +31,7 @@ The portable `spfx-ide` skill ships in [`packages/ide/skills/spfx-ide/SKILL.md`]
31
31
 
32
32
  ## Preview a consumer component
33
33
 
34
- The npm package name is `@spfx-fast/spfx-workbench`. Version `0.1.1` is published; this checkout prepares public version `0.1.2`. Install the published package in an SPFx project and run the CLI from that project's root:
34
+ The npm package name is `@spfx-fast/spfx-workbench`. Version `0.1.2` is published; this checkout prepares public version `0.1.3`. Install the published package in an SPFx project and run the CLI from that project's root:
35
35
 
36
36
  ```sh
37
37
  npm install --save-dev @spfx-fast/spfx-workbench
@@ -74,7 +74,7 @@ This is an early consumer-loader slice. It supports explicit JSON props and the
74
74
 
75
75
  ## How this fits with the SPFx Fast tools
76
76
 
77
- Use [`@spfx-fast/ide`](packages/ide/README.md) as the thin developer and agent entry point. The registry has Workbench 0.1.1 and IDE 0.1.0. IDE 0.1.1 failed publication at npm; the prepared 0.1.2 adds Workbench as a dependency and automatic skill placement. Fix the IDE npm Trusted Publisher before publishing Workbench 0.1.2 and then IDE 0.1.2. Until the IDE release succeeds, registry installs do not include Workbench routes or the skill hook. The candidate's `spfx-ide` routes to focused tools; installing it as a project devDependency or globally places Agent Skills guidance in supported skill directories unless lifecycle scripts are disabled. This confirms file placement, not discovery by every agent; check the agent's own skills list where available. Global CLI use also needs npm's global bin directory on `PATH`. Workbench owns component preview, synthetic context/API replay, diagnostics, capture, and Heft launch. The focused companion packages have separate jobs:
77
+ Use [`@spfx-fast/ide`](packages/ide/README.md) as the thin developer and agent entry point. Workbench 0.1.2 and IDE 0.1.2 are published. IDE 0.1.2 adds Workbench routes and automatic skill placement; the 0.1.1 npm publication attempt failed before the Trusted Publisher was corrected. This checkout prepares Workbench 0.1.3 and IDE 0.1.4. The `spfx-ide` CLI routes to focused tools; installation as a project devDependency or globally places Agent Skills guidance in supported skill directories unless lifecycle scripts are disabled. This confirms file placement, not discovery by every agent; check the agent's own skills list where available. Global CLI use also needs npm's global bin directory on `PATH`. Workbench owns component preview, synthetic context/API replay, diagnostics, capture, and Heft launch. The focused companion packages have separate jobs:
78
78
 
79
79
  - [`@spfx-fast/playwright`](https://www.npmjs.com/package/%40spfx-fast/playwright) runs authenticated browser tests against a real SharePoint page.
80
80
  - [`@spfx-fast/knowledge`](https://www.npmjs.com/package/%40spfx-fast/knowledge) provides the SPFx agent skill and debugging references; use it to guide the tools, not as a runtime dependency.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@spfx-fast/spfx-workbench",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "Local SPFx component preview, diagnostics, SharePoint API capture and replay, and Heft debugging tools.",
5
5
  "publishConfig": {
6
6
  "access": "public"