Shuo Wu

@johnstondo This error is thrown when fails to parse JSON string, have you manually modified the storage values? Probably try clear your browser storage and try login again?

@chadmg The safari issue may cause by the `Prevent cross-site tracking` was enabled in the browser. With the current version of okta-auth-js, you can add `offline_access` to scopes to enable...

@jchabotamica You probably can try the [resolve.mainFields](https://webpack.js.org/configuration/resolve/#resolvemainfields) config in webpack to tell the bundler to load okta-auth-js ESM bundle from the [module](https://github.com/okta/okta-auth-js/blob/master/package.json#L10) field. From the screenshot, looks like it loads...

@sdiltsDNRC Thanks for the suggestion! We will consider setting a proper target in the next major version. To handle the warning, you can add `@babel/runtime-corejs3` to angular's commonjs allow list...

@GreatEarl We are still working on "the longer term" solution. For now, you can follow the suggestion in https://github.com/okta/okta-auth-js/issues/371#issuecomment-643431027 to use the `custom domain` solution as a workaround.

@x87 Thanks for reporting the issue! Internal Ref: OKTA-418956

Internal Ref (only store encoded token in cookie): OKTA-413942

@rwev Thanks for reporting the bundle size issue! We also noticed the issue and are re-design a tree shaking friendly architecture for this SDK.

@Mak2492 Have you figured out a way to unblock the IE11 issue?

@garrettmac With calling the [signOut](https://github.com/okta/okta-auth-js#signout) method, it kills the Okta SSO session. But other devices app session may depend on how you define it in your app. Like in the...