Release1.24.1

• Fixing AOT issues

Release 1.24.0

• Cannot read property 'nativeElement' of undefined (1430)
• Update supported versions (1425)
• Adding redirect to route path description (1423)
• Adding try catch with workaround to solve bug (1418)
• Sanity for AppRef.isStable observable (1417)
• Update libraries & Compability (1416)
• Define selectedComponentProperty in the way it could be redefined (1411)

Release 1.23.0

• Fix component info scrolling firefox (1360 & 1376)
• Handle string provider type in Description.getProviderDescription (1367)
• Remove from README duplicate at table of contents (1371)

Release 1.22.0

Bug Fixes

• Fix HMR issue.
• Fix change-detection parsing issue (1344)

Release 1.21.0

Bug Fixes

• Fix state not showing issues (1340)

Release 1.20.0

• Angular 7 support
• Bump npm package versions
• Remove beta from Firefox

Release 1.19.0

• Bug fixes (angularJS hybrid app compatibility, component tree refreshing, and more state panel issues)
• Highlighter/selection tool improvements

Release 1.18.0

Fixes:

• States not showing up for some components (there might be still some edge cases out there that cause this issue, but all known occurrences are fixed for).
• Page slowing down to a freeze due to interaction between Augury and other extensions (notably Redux DevTools)
• Angular JIT compiler error due to reflect-metadata. (reflect-metadata is no longer included in the Augury build)

Small Tweaks:

• "loading" / "no state to show" messages during component state inspection

Release (1.16.2)

1.16.2

• Fix bug: component states dont show up sometimes.
  • (1254)
  • (1114)
  • (1300)
  • (1301)
• Angular AOT compilation (for the front end)
• Webpack 4 upgrade
• Local fonts
• Different builds for Firefox / Chrome
• Remove unnecessary uses of eval() and new Function()
• Angular 6 compatibility

Release 1.16.0

1.16.0

• Add extendible build configurations for different versions of the augury package (currently for firefox and canary builds).
• Fix edge case bugs that crashed augury (commonly affecting PrimeNG users)
• Fix Angular application detection bug
• Angular 6 compatibility