@bluestep-systems/bspecs 0.11.0 → 0.11.1
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 +3 -2
- package/package.json +1 -1
- package/src/scaffold.js +5 -3
package/README.md
CHANGED
|
@@ -32,11 +32,12 @@ The npm install needs no token, but the `/b6p-pull`, `/b6p-push`, and `/b6p-audi
|
|
|
32
32
|
work until you set your BlueStep platform credentials:
|
|
33
33
|
|
|
34
34
|
```sh
|
|
35
|
-
npx b6p auth set
|
|
35
|
+
npx -p @bluestep-systems/b6p-cli b6p auth set
|
|
36
36
|
```
|
|
37
37
|
|
|
38
38
|
Run this **once per machine** — credentials are stored globally in `~/.b6p`, not per project. This is
|
|
39
|
-
unrelated to the npm registry.
|
|
39
|
+
unrelated to the npm registry. (The `-p` form is required because `b6p` is a project-local
|
|
40
|
+
devDependency; bare `npx b6p` resolves only inside a scaffolded project, where `npx b6p …` works.)
|
|
40
41
|
|
|
41
42
|
## Usage
|
|
42
43
|
|
package/package.json
CHANGED
package/src/scaffold.js
CHANGED
|
@@ -83,10 +83,12 @@ export async function scaffold(answers) {
|
|
|
83
83
|
[
|
|
84
84
|
'Next step — set your BlueStep platform credentials (required, once per machine):',
|
|
85
85
|
'',
|
|
86
|
-
' npx b6p auth set',
|
|
86
|
+
' npx -p @bluestep-systems/b6p-cli b6p auth set',
|
|
87
87
|
'',
|
|
88
|
-
'
|
|
89
|
-
'
|
|
88
|
+
'Run that from anywhere (it fetches the CLI on the fly). Inside this project after `npm',
|
|
89
|
+
'install`, plain `npx b6p ...` also works. Until credentials are set, the /b6p-pull,',
|
|
90
|
+
'/b6p-push, and /b6p-audit skills cannot run. Credentials are stored globally in ~/.b6p,',
|
|
91
|
+
'so you only do this once — not per project.',
|
|
90
92
|
].join('\n')
|
|
91
93
|
);
|
|
92
94
|
}
|