aurelia-history-browser v0.9.0

Bug Fixes

• all:
  • update to latest plugin api (85418be2)
  • update compiler (6be59964)
• bower: correct semver ranges (9c7f33f5)
• build:
  • update linting, testing and tools (9ad076d6)
  • add missing bower bump (5b4cc6f3)
• history:
  • Improved previous pushState security fix by only fixing up double slashes in fra (9d7565a1)
  • fixed regression issue which added double slashes to the pushState fragment (57983341)
  • normalize fragments with a leading slash (66998d87)
  • fix incorrect falsey check in getFragment (34cb8224)
• history-browser:
  • verify that window is defined in ctor (78449060)
  • Use correct import for core-js We were previously using `import core from core-j (45d51c8c)
  • support scheme-relative URLs in BrowserHistory.navigate() (16fcfdd7)
• index: update to latest configuration api (a3681cfb)
• normalize-fragment: fix getFragment() to return normalized values (5cb9bf30)
• package:
  • update aurelia tools and dts generator (ee59abbc)
  • change jspm directories (2b161b23)
  • update dependencies (d56c60df)
  • update dependencies (0f9bc51a)
  • update Aurelia dependencies (770590c2)
  • add es6-shim dependency for Object.assign (517b7e8e)
  • update dependencies to latest (cdd1c232)

Features

• all: leverage the PAL (01cd524c)
• build: update compiler and switch to register module format (ff2a572b)
• docs: generate api.json from .d.ts file (80fd2e30)
• history: enable usage as plugin (f73c967b)
• history-browser:
  • move link handler from router and allow custom implementations (f0129d89)
  • adjust default navigate options (0f17175d)
  • allow replace option to trigger a navigation to the same fragment (1eab2945, closes #201)

Breaking Changes

• trigger now defaults to true when other options are specified, and options must be passed as an object; a boolean is no longer supported as a shortcut for trigger.

  (0f17175d)