v1.2.0

New features

• There is a new Ravelin.track.event(name, [props]) method for sending custom events to the Ravelin API.
• A new Ravelin({id: ...}) constructor option allows you to set a device ID instead of Ravelin generating one for you. The id you provide can be either string or Promise form. If a given Promise errors or resolves to an empty value, Ravelin's own device ID tracking will kick in again, so you may still want to configure cookie below.
• A new Ravelin({cookie: "ravelinDeviceId"}) constructor option allows you use a different cookie name for the Ravelin device ID. If you already have a device ID in a cookie then this is a nice way to ask Ravelin to use it. Ravelin will attempt to re-create the cookie with the same value if it notices that it disappears. Note that adding this option, or changing it will lose all existing device IDs as we now look somewhere else for them, so only set when first integrating.
• A new Ravelin({cookieExpiryDays: 365}) constructor option allows you to set the lifetime in days that a device ID cookie we set will persist. The default is 365.
• The default Promise that Ravelin will use is now exported through Ravelin.Promise so that you can use it as a construction option when using the +promise bundles.

Bug fixes

• Page-load events were being submitted with type and name swapped. They've been put back the correct way around now.
• The autogenerated table of contents on the README now correctly links to headings that contain </> symbols, e.g. ravelin.core.id(): Promise<string>.