@schibsted/account-sdk-browser - npm Package Versions

v3.0.0-rc.15 (2018-09-06)

New features

• Support for new Identity.login parameters: tag, teaser and maxAge
• ITP: There are explicit methods in Identity for users that don't use the login method. See the docs for showItpModalUponReturning and suppressItpModal if you're interested

Breaking changes (ish)

• The Identity.loginUrl method used to take a lot of arguments, and with this release it was about to become even more (with the added tag, teaser and maxAge params mentioned above). This release changes the signature to have a single options object instead of the argument list. In this case we made it backwards-compatible, so it won't break (YET!) if you continue using an argument list. Beware though, that passing a list of arguments is considered DEPRECATED as of now
• The es5 folder now contains both minified and unminified code. The minified ones have the .min.js suffix. Before, only minified files were published, so if you're using those, you might suddenly have bigger files than you did before. Sorry.. 🤷🏼‍

Fixes

• #76 — Login on Chrome/iOS should now work once again

v3.0.0-rc.14 (2018-09-03)

Changes

• The only change is adding a typings file to the es5 folder. There are no functional changes from rc.13

v3.0.0-rc.13 (2018-08-31)

Fixes

• The "Safari 12 ITP2 workaround" from v3.0.0-rc.11 had a bug where we passed the wrong query parameter to the ITP dialog, so the dialog then failed to post a message back to the parent page. In conclusion; calls to Identity.hasSession would still fail 😭.

v3.0.0-rc.12 (2018-08-30)

This release is identical to rc.11 but includes index.d.ts in the npm package.

v3.0.0-rc.11 (2018-08-30)

New features

• Initial support for Safari 12. For users of this browser, there could be issues related to Intelligent Tracking Prevention (ITP) v2. For the people who experience it, it would be impossible to detect whether you're logged in or not from a given site (because cookies to Schibsted account would be blocked because it's a third party). The Apple way to solve this, is to call requestStorageAccess from an iframe, and let the user choose "Allow" in a scary Safari dialog. Then cookies will once more be allowed to go to that third party. This SDK will now work around this by showing a friendlier dialog before calling requestStorageAccess so people are hopefully more inclined to click "Allow".

v3.0.0-rc.10 (2018-08-10)

Fixes

• #68 — Cache was not cleared after calling Identity.logout() or Identity.enableVarnishCache

v3.0.0-rc.9 (2018-08-08)

Fixes

• Upgraded regenerator-runtime to fix this CSP issue (courtesy of @henninga)
• #64 — This issue was fixed in two ways. First, by changing the implementation so we set the Varnish cookie on every call to hasSession (before we didn't do so when a hasSession returned cached data). Second, we introduced an optional parameter expiresIn on the Identity.enableVarnishCookie where you can override the default expiry of the Varnish cookie.
• #54 — Ensure that we clear the Varnish cookie when a user logs out.

v3.0.0-rc.8 (2018-07-17)

Fixes

• Remove not logged in user cache on login call https://github.com/schibsted/account-sdk-browser/issues/62