@meshagent/meshagent-ts-auth 0.36.3 → 0.37.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/CHANGELOG.md CHANGED
@@ -1,3 +1,19 @@
1
+ ## [0.37.1]
2
+ - Added `useAuth` to the React auth package to handle OAuth redirect/callback, token refresh, and profile loading without React Query, plus a `useEnsureLogin` compatibility wrapper.
3
+ - React auth `useMAuthResponse` now deduplicates token exchanges per callback parameters to avoid repeated exchanges on re-renders.
4
+ - Breaking: React auth no longer exports React Query `QueryClient` or `QueryClientProvider`.
5
+ - Breaking: `useLoginScope` now delegates to `useAuth` and defaults the OAuth scope to `email`.
6
+ - Breaking: the `staticAuthorization` helper was removed from the React room connection utilities.
7
+ - React dev terminal hooks now return `RefObject`-typed `containerRef` values for stronger typing.
8
+ - Meshagent TS client now normalizes binary request bodies for fetch and includes TypeScript declarations for runtime entrypoint functions.
9
+
10
+ ## [0.37.0]
11
+ - Breaking: Database client now supports `json`, `uuid`, `list`, and `struct` types with typed wrappers (DatabaseJson/DatabaseStruct/DatabaseExpression/DatabaseDate/DatabaseUuid); list/struct values must be wrapped and update now takes `values` only.
12
+ - Breaking: Containers build now streams build contexts (start/data chunks) with `mountPath`/`chunks` and removes `start_build`.
13
+ - Breaking: Toolkit/hosting refactor replaces RemoteToolkit with startHostedToolkit/HostedToolkit, removes ToolkitConfiguration and `supports_context`, and updates React/Tailwind helpers to start hosted toolkits.
14
+ - Participant tokens now include LLM grants and richer grant serialization (including allowed toolkits and extra payload preservation), and schema helpers add `json`/`uuid` data types.
15
+ - The JS SDK now exports its version constant for client-side visibility.
16
+
1
17
  ## [0.36.3]
2
18
  - Storage client now supports move operations and emits file moved events.
3
19
  - Secrets client now supports existence checks.
package/README.md CHANGED
@@ -31,20 +31,28 @@ The starter tests focus on the areas most likely to break in day-to-day auth wor
31
31
 
32
32
  Add new regression tests in `test/*.test.ts` as issues come up.
33
33
 
34
- ## Before You Start
34
+ ## Before You Get Started
35
35
 
36
- You need an OAuth client in Meshagent Studio.
36
+ Create an OAuth client in Meshagent Studio and register your callback URL.
37
37
 
38
- 1. Sign in to `https://studio.meshagent.com`.
39
- 2. Open `OAuth Clients`.
40
- 3. Create a new OAuth client.
41
- 4. Add your callback URL.
38
+ 1. Sign in to https://studio.meshagent.com.
39
+ 2. Select your project
40
+ 3. Open "OAuth Clients" at the bottom of the left menu
41
+ 4. Click "New OAuth Client" button at the top
42
+ 5. Add
43
+ - name for the client id (e.g. "My App")
44
+ - enter "email" for the scope
45
+ - add redirect URIs (e.g. "http://localhost:3000/")
46
+ 6. Upon successful creation, you will see the client id and client secret. Click "Copy" button to copy the client id and client secret to clipboard. You will need them later when you run the app.
42
47
 
43
- You will use:
44
48
 
45
- - `serverUrl`: your Meshagent server, for example `https://api.meshagent.com`
49
+ You will need these values throughout the examples:
50
+
46
51
  - `oauthClientId`: the OAuth client ID from Studio
47
- - `callbackUrl`: the URL Meshagent redirects back to after login
52
+ - `callbackUrl`: the URL Meshagent redirects back to after login - this must match the redirect URI you registered in Studio
53
+
54
+ Optional
55
+ - `serverUrl`: your Meshagent API base URL, uses `https://api.meshagent.com` as default
48
56
 
49
57
  ## What The Package Stores
50
58