@passflow/react 0.7.1 → 0.8.1

package/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Changelog
+
+All notable changes to `@passflow/react` are documented in this file.
+
+## [0.8.1] - 2026-07-28
+
+Version 0.8.1 is the first registry release after 0.7.1 and includes the previously unreleased 0.8.0 device-verification work.
+
+### Added
+
+- A typed, Storybook-backed `LoginScreen` component system covering credential, passkey, code-entry, invitation, device-approval, status, and general-error states.
+- RFC 8628 device verification through `DeviceVerifyFlow`, `useDeviceVerify`, typed device errors, and explicit device approval screens.
+- Shared CLI browser and QR authentication state mapping through the component library.
+- Bundled country flags and an improved international phone field with no runtime dependency on third-party flag assets.
+- Storybook accessibility tooling and Playwright coverage for authentication states, interactions, responsive layouts, themes, and accessibility.
+- Typed authentication error classification and shared login-theme and invitation-chrome mapping utilities.
+
+### Changed
+
+- Sign-in, sign-up, invitation, CLI authentication, device verification, passwordless verification, and error screens now consume the shared UI component library instead of maintaining flow-local visual implementations.
+- Authentication styling now resolves through the existing `--passflow-*` design tokens, with Storybook serving as the supported-state catalog.
+- Build, Storybook, Vitest, Playwright, Vite, and pnpm tooling were upgraded and aligned with CI.
+- The npm package now rebuilds during `prepack` and excludes demo, test, Storybook, and Playwright declarations from the published artifact.
+
+### Fixed
+
+- OIDC credential flows no longer cancel the relying party callback with a competing post-login navigation after the interceptor has followed `redirect_url`.
+- Sign-in and sign-up user-facing errors no longer expose raw backend or redirect details.
+- Password, phone, icon, switch, provider, focus, loading, and validation states received accessibility and interaction fixes.
+
+[0.8.1]: https://github.com/MadAppGang/passflow-react-sdk/compare/v0.7.1...v0.8.1

package/README.md

@@ -56,6 +56,22 @@ pnpm build
 
 ## Local Development
 
+### Component development with Storybook
+
+The visual source of truth lives in `src/components/ui` and is catalogued in Storybook.
+
+```sh
+pnpm storybook
+```
+
+Before reusing a new visual state in a flow, add it to the owning UI component and its co-located `*.stories.tsx` file. Verify the static catalog with:
+
+```sh
+pnpm build-storybook
+```
+
+Flows and form controllers should map domain state and callbacks into library components rather than creating or styling controls in place. See [`CLAUDE.md`](./CLAUDE.md) for the repository boundary.
+
 ### Using Local Passflow JS SDK
 
 For local development and testing with a local version of the Passflow JS SDK, you need to:
@@ -98,32 +114,26 @@ we are using pnpm. Please ansure you have it in the system.
 
 ## UI Testing
 
-We are using playwright to run UI tests.
-
-First, ensure you have all runtime binary enabled:
+All UI behavior and Storybook state tests use Playwright. Install Chromium once:
 
-```
-pnpm exec playwright install
+```sh
+pnpm exec playwright install chromium
 ```
 
-and then feel free to run the tests:
+Run the complete UI suite headlessly:
 
+```sh
+pnpm test
 ```
-pnpm run test:ui
-```
-
-### Writing your own ui tests.
 
-You can find a tests in the `./tests` frolder.
+Or launch Playwright's interactive test UI:
 
-Please create the new files using the current tests as a reference.
-
-To run the playwright in the design mode with ui, run the follwoing command:
-
-```
-pnpm playwright test --ui
+```sh
+pnpm test:ui
 ```
 
+Both scripts automatically start the demo app and Storybook. `pnpm test` uses the economical headless configuration, while `pnpm test:ui` retains traces and a final full-page screenshot for every successful test. Select a runnable leaf test in Playwright UI to inspect its action timeline, DOM snapshots, and screenshot attachment. Tests live in `playwright/tests`; component-state tests render the real Storybook stories rather than recreating components in a test-only harness. Vitest remains for non-visual hooks, controllers, and utility logic.
+
 ## Installation
 
 ```bash