@meshagent/meshagent-ts-auth 0.35.6 → 0.35.8

package/CHANGELOG.md

@@ -1,2 +1,6 @@
+## [0.35.8]
+- `ensureLogin` now uses the current page as the OAuth callback (no stored marker/URL), strips OAuth query params on return, and refreshes the current user profile when already logged in.
+- JavaScript/TypeScript storage download examples now use storage upload and decode bytes, and the docs example build ignores generated JS artifacts alongside TypeScript sources.
+
 ## [0.30.0]
 - Initial TypeScript/React auth package based on `meshagent-flutter-auth`.

package/README.md

@@ -74,10 +74,10 @@ The simplest browser login flow is a single `await ensureLogin(...)` call.
 `ensureLogin(...)` handles all of these cases:
 
 - the user is already logged in, so it returns immediately
-- the current URL is the configured callback URL, or it carries the default Meshagent callback marker, and contains `?code=...`, so it exchanges the code, stores the session, loads the current user, and removes auth query params from the URL
+- the current URL contains `?code=...` and matches the configured callback URL, or when `callbackUrl` is omitted matches the current page URL after auth query params are stripped, so it exchanges the code, stores the session, loads the current user, and removes auth query params from the URL
 - the user is not logged in yet, so it generates PKCE values, stores the verifier, and redirects to `/oauth/authorize`
 
-When you omit `callbackUrl`, `ensureLogin(...)` uses the current page as the callback URL and adds `ma_origin=meshagent_auth` so it can tell a Meshagent OAuth return apart from unrelated query params. That marker is removed after a successful callback exchange.
+When you omit `callbackUrl`, `ensureLogin(...)` uses the current page as the callback URL. After the OAuth redirect returns, it strips the auth query params from the current URL and reuses that same URL for the token exchange.
 
 ## Example: Ensure Login
 
@@ -224,9 +224,9 @@ Run `npm run build` to generate `dist/browser/ma-auth.global.js`.
 Serve that file from your app or copy it into your static assets, then include it with a classic script tag:
 
 ```html
-<script src="/assets/ma-auth.global.js"></script>
+<script src="https://storage.googleapis.com/cdn.meshagent.com/latest/ma-auth.global.js"></script>
 <script>
-  const auth = window.maAuth.MeshagentAuth.current;
+  const auth = window.meshagent.auth.MeshagentAuth.current;
   console.log(auth.isLoggedIn());
 </script>
 ```
@@ -240,23 +240,23 @@ TypeScript consumers using the global bundle can add:
 The browser-global API matches the module API, so the earlier examples translate directly. For example:
 
 ```html
-<script src="/assets/ma-auth.global.js"></script>
+<script src="https://storage.googleapis.com/cdn.meshagent.com/latest/ma-auth.global.js"></script>
 <script>
   async function ensureMeshagentSession(provider) {
-    await window.maAuth.ensureLogin({
+    await window.meshagent.auth.ensureLogin({
       serverUrl: "https://api.meshagent.com",
       callbackUrl: "http://localhost:3000/auth/callback",
       oauthClientId: "YOUR_OAUTH_CLIENT_ID",
       provider,
     });
 
-    if (!window.maAuth.MeshagentAuth.current.isLoggedIn()) {
+    if (!window.meshagent.auth.MeshagentAuth.current.isLoggedIn()) {
       return;
     }
 
     console.log(
       "Logged in:",
-      window.maAuth.MeshagentAuth.current.getSnapshot(),
+      window.meshagent.auth.MeshagentAuth.current.getSnapshot(),
     );
   }
 <\/script>