- Update build dependencies and drop dependency to loader-utils in the Webpack loader package. Keeps dependabot and npm audit happy, should not cause breaking changes.
- Update build dependencies to keep dependabot and npm audit happy. Should not cause breaking changes
- Update build dependencies to keep dependabot and npm audit happy. Should not cause breaking changes
- Fix a non-reported bug in standalone package, where
readyState
of the websocket client wasn't read correctly
- Keep the prototype of the original directive, see PR #26. Thanks @martonbrunner!
- Fixes #24.
AngularJS versions older than 1.7 supported passing component/directive bindings
to the
this
context of a controller constructor. ng-hot-reload was't complying with this behaviour and the bindings were available only in $onInit lifecycle event. This is fixed in 592f3cd728. If the AngularJS version is lower than 1.7 and there are bindings to pass, construction is done lazily and the this-context of the constructor is fixed to include the bindings before being called.
- Fix a crash when using webpack loader without source maps
- Change default code that is used to require angular in webpack loader (should not be a breaking change).
- Add souce map support #19
- Drop support for Node versions older than 8
- Fixed/added ngAnimate support #14 759484a
- Minor updates to the demo, made it clearer that the loader is not supposed to be used in production 97b6b52
- Switched to using slightly better Webpack devtool f53eaf2
- Updated build dependencies, no breaking changes
- Updated build dependencies, no breaking changes
- Fix issue #4
- Remove special support for UI-router UI-router supports routing to a component, which works much better with this library than the hacky route reloading that we tried to do before.
- Fix an issue that caused only the first component to update in cases where there were more than one instances of the component active
- Add options support for the Webpack loader