@synqauth/js 0.2.0 → 0.4.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/README.md CHANGED
@@ -4,7 +4,7 @@ Synq's framework-agnostic client: sign-in and sessions in the browser, the accou
4
4
 
5
5
  Synq is customer identity for businesses: an OpenID Connect issuer for each of your brands, with Solana wallet, social, email and passkey sign-in. The documentation is at [docs.synq.build](https://docs.synq.build).
6
6
 
7
- This package is at 0.x and hasn't been published yet: its API can change in any release until Synq's first customer depends on it.
7
+ This package is at 0.x, so a minor release can change its API: see its CHANGELOG.md.
8
8
 
9
9
  ## The account API
10
10
 
@@ -33,8 +33,14 @@ const { data: request } = await account.accounts.link('wallet')
33
33
  if (request) await synq.signIn(linkSignIn(request))
34
34
  ```
35
35
 
36
+ `accounts.link()` takes any method `accounts.linkable()` lists. For `passkey` it answers the hosted add-passkey sign-in instead of a link request, sent the same way with `linkSignIn`.
37
+
36
38
  Every call answers `{ data, error }` and never throws for what Synq answers; branch on `error.code`.
37
39
 
38
40
  ## License
39
41
 
40
42
  MIT
43
+
44
+ ## Synq customer email work
45
+
46
+ `solveEmailWork(challenge, { signal })` is a public bounded solver for the self-hosted email-work protocol, in plain JavaScript: it needs no WebCrypto and yields between short slices of work. Current own-UI email sends solve and retry at most once when Synq’s customer brand requires it. `flow.cancelEmailWork()` cancels local computation; newer operations invalidate older work. It does not enable work on tenant brands or prove authentication. See the [own-UI protocol guide](https://docs.synq.build/guides/own-ui-sign-in). Runtime activation remains staged until migration, SDK and browser performance validation.