cli-setu 0.2.8 → 0.2.9
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/bin/setu.js +1 -1
- package/package.json +1 -1
- package/src/pair.js +15 -1
package/bin/setu.js
CHANGED
|
@@ -91,7 +91,7 @@ async function main() {
|
|
|
91
91
|
const config = readConfig();
|
|
92
92
|
if (!config || !config.deviceToken) {
|
|
93
93
|
const { pair } = require('../src/pair');
|
|
94
|
-
await pair(AUTH_SERVER, AUTH_SERVER_PUBLIC);
|
|
94
|
+
await pair(AUTH_SERVER, AUTH_SERVER_PUBLIC, { standalone: false });
|
|
95
95
|
}
|
|
96
96
|
require('../src/supervisor');
|
|
97
97
|
}
|
package/package.json
CHANGED
package/src/pair.js
CHANGED
|
@@ -8,7 +8,7 @@ const qrcode = require('qrcode-terminal');
|
|
|
8
8
|
const { loadOrCreateConfig, writeConfig, hasKeypair } = require('./config');
|
|
9
9
|
const { generateKeypair, publicKeyToBase64, privateKeyToBase64 } = require('./crypto');
|
|
10
10
|
|
|
11
|
-
async function pair(authServer, authServerPublic) {
|
|
11
|
+
async function pair(authServer, authServerPublic, { standalone = true } = {}) {
|
|
12
12
|
const config = loadOrCreateConfig();
|
|
13
13
|
|
|
14
14
|
// Section 1 E2E: generate this device's own keypair up front, before
|
|
@@ -125,6 +125,20 @@ async function pair(authServer, authServerPublic) {
|
|
|
125
125
|
}
|
|
126
126
|
}
|
|
127
127
|
|
|
128
|
+
// Real gap found by testing (PM report): a first-time user had no clear
|
|
129
|
+
// next step after pairing succeeded - pairing a device and starting a
|
|
130
|
+
// real terminal session are deliberately separate commands (one laptop
|
|
131
|
+
// can run several sessions, switch CLIs across restarts, etc.), but
|
|
132
|
+
// nothing here ever told a first-time user that distinction, or what
|
|
133
|
+
// to actually type next. Only shown for an explicit, standalone
|
|
134
|
+
// `cli-setu pair` - bin/setu.js's own bare-`cli-setu` flow calls this
|
|
135
|
+
// function too (auto-pairing an unpaired machine before immediately
|
|
136
|
+
// starting a session right after), where this message would be
|
|
137
|
+
// immediately followed by the session actually starting anyway.
|
|
138
|
+
if (standalone) {
|
|
139
|
+
console.log('[cli-setu] Run `cli-setu` in a project folder to start your first session.');
|
|
140
|
+
}
|
|
141
|
+
|
|
128
142
|
return config;
|
|
129
143
|
}
|
|
130
144
|
|