v5.0.0

• This version is the exact same as the previous alpha.

v5.0.0-alpha.7

• Added hasLink on Resources and Representations.

v5.0.0-alpha.6

• Fixed a bug in getOptions()

v5.0.0-alpha.5

• Added a preferPush() method to 'Follower' objects, allowing you to
  automatically send [Prefer-Push][3] headers when following links.
• Moved all functionality related to the 'Repreprentor' in a utility class,
  making both the Ketting and Resource classes simpler.
• Simplified Resource.refresh(), making it easier to read and do less work.
• When calling .post(), the function will only return a new resource if the
  HTTP response code was 201.
• If the HTTP response code to a post() call was 205, it will now return
  the current resource.
• Removed the logic for automatically adding Prefer-Push headers. This was
  unreliable, and usually did the wrong thing. The new system is 100% opt-in
  and developer-driven.
• Added Ketting.getOptions() to return a list of options that were passed to
  Ketting. The options will be enhanced with OAuth2 refresh and access tokens
  as they become available, meaning that it can be used to place in
  LocalStorage to remember sessions. This feature is experimental and
  incomplete. It might change even in minor versions.

5.0.0-alpha.4

• This version is identical to the last, but fixes an issue on npmjs.com.
  Updating is not needed.

5.0.0-alpha.3

• It's now possible to tell Ketting to prefetch every resource when following
  links via Resource.follow('foo').preFetch().
• Link and LinkNotFound are now both exported.
• Documentation overhaul.

v4.0.4

• This version is identical to the last, but fixes an issue on npmjs.com.
  Updating is not needed.

4.0.3

• The internal resource cache will now evict items for any non-safe HTTP
  method.

4.0.0

• #129: Using the package in non-typescript node.js now wortks with a simple
  const Ketting = require('ketting').
• #129: Fixed the browser distribution. the Ketting constructor is
  registered globally again.

Included from alpha release:

• The old format for OAuth2 setup is now no longer supported.
• It's now possible to specify per-domain authentication using wildcards.
  This allows you to set up specific authentication credentials for specific
  domains. This might be useful in case you talk to multiple API's with a
  single client.

3.0.0

• Switched OAuth2 implementation from client-oauth2 to fetch-mw-oauth2.
  This adds support for authorization_code auth, removes 11 dependencies and
  reduces the minified Ketting build from 69KB to 28KB.
• OAuth2 options now have a new format. The old format is still supported, but
  will be removed from a future version.
• The baseHref propertyname was renamed to Context on the Link type. The
  new name matches the name from RFC8288. This is a small BC break.