authts/oidc-client-ts

Summary src/User.ts drops state and url_state when the authenticated User is persisted, so the first storeUser() / _loadUser() round-trip strips those fields from later getUser() results and from refresh-token silent renew. Repro Sign in with custom state, for example: await mgr.signinRedirect({ state: { returnTo: /billing }, url_state: tab=security, }) Complete the callback and confirm the first User still has those values: const user = await mgr.signinCallback() user.state // { returnTo: /billing } user.url_state // tab=security Call await mgr.getUser() or let signinSilent() take the refresh-token path. The loaded user now has state === undefined and url_state === undefined. Expected Once a User has been stored, later getUser() calls and silent-renew updates should preserve the original state / url_state just like the initial callback user. Actual UserManager.storeUser() persists a JSON blob from User.toStorageString(), but that blob only contains tokens, profile, scope

RefreshState is marked @public in the source and is included in the type declarations (export declare class RefreshState). It's also required to call the public OidcClient.useRefreshToken() method, since UseRefreshTokenArgs.state is typed as RefreshState. However, RefreshState is not actually exported from the ESM, UMD, or browser bundles. This means consumers using OidcClient directly (rather than UserManager) cannot construct a RefreshState at runtime to call useRefreshToken. Steps to reproduce: Import RefreshState from oidc-client-ts in a project using the ESM bundle (e.g. via Vite/Rollup) Build fails because RefreshState is not exported from the bundle import { OidcClient, RefreshState } from 'oidc-client-ts'; // RefreshState is undefined at runtime ** Repro repo** https://github.com/eugenioenko/oidc-client-ts-refresh-state-bug-repro Stackblitz https://stackblitz.com/github/eugenioenko/oidc-client-ts-refresh-state-bug-repro, just run npm run build src/main.js (1:21): "RefreshStat