@yahoo/uds 1.5.0 → 1.6.0

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/cli/README.md CHANGED
@@ -179,6 +179,22 @@ Commands are organized in a tree structure in `uds/cli/commands`. The root comma
179
179
 
180
180
  Adding nested commands, i.e. `uds expo dev` does work correctly when UDS is consumed from npm. As a workaround, please see code for expo/expo.ts for re-routing sub-commands from the root command file. To verify your CLI command works correctly you should run `npm pack` within the packages/uds directory. Once you have your generated tarball you should copy that tarball to a test application such as https://github.com/yahoo-uds/uds-nextjs-demo, then add `"@yahoo/uds": "file:./tarball-generated-from-npm-pack.tgz` to it's dependencies and run an install. Now you should be able to run `bun uds [your command name]` to test your functionality.
181
181
 
182
+ ### Testing the login flow
183
+
184
+ To test the login flow, the CLI starts a web server and opens browser window to
185
+ a login page in Configurator. In prod, it opens https://config.uds.build/login.
186
+ In local dev, http://localhost:4001/login is opened.
187
+
188
+ In the root of the UDS monorepo, run the following commands:
189
+
190
+ ```
191
+ # Start configurator app web server:
192
+ turbo --filter uds-configurator dev
193
+
194
+ # Run the CLI login command:
195
+ bun run --cwd packages/uds uds login
196
+ ```
197
+
182
198
  ### API Reference
183
199
 
184
200
  Bluebun comes with a number of built-in utilities that are exported from the main `bluebun` package. See [reference guide](https://github.com/jamonholmgren/bluebun/blob/main/docs/reference.md) for more.
Binary file
Binary file