5.3.2

• fix(test): avoid destroying progressRef which is not yet initialized, closes #217 in 850c65f

5.3.1

• feat(http): Ignore HTTP request by appending ignoreProgressBar to request's headers, closes #234 in a625d01.
• enhance(core): Increase spinner speed, in 0381cd3.
• refactor(core, http, router): Deprecate forRoot(config?) usage, config can be provided using withConfig(config) instead, in 1b76e0b.

This removes the need to import NgProgressModule in your root module, in other word, you no longer need to include this library in the main bundle if you are using it in lazy loaded modules.

Breaking changes

• Change NgProgressModule.forRoot() to NgProgressModule
• If you use custom config NgProgressModule.forRoot(config), then change it to NgProgressModule.withConfig(config)

The same applies on NgProgressHttpModule and NgProgressRouterModule

5.2.1

• Update packages peerDependecies to remove npm warnings in Angular 7
• Update project to Angular 7

5.2.0

• feat(core): Add [fixed] option, to disable the default progress bar fixed position, closes #212 in fff21f3.
• feat(router): Add startEvents and completeEvents options, closes #211 in 0f7effe.
• refactor(core): Refactor progressbar destroyer function.
• refactor(core): change progressbar state from NgProgressRef.state$ to NgProgressRef.state.
• refactor(core): Use Map<string, NgProgressRef> for instances instead of just an object.
• refactor(core): Remove helper functions exposed in NgProgress.

Breaking Changes

• The following functions has been remove from NgProgress service: setConfig(), start(), set(), inc(), complete(), isStarted(), started(), completed(), destroy().

Before:

It was possible to use these functions from NgProgress service directly

ngProgress.start();

After:

These functions are accessed by the NgProgressRef instance

const progressRef: NgProgressRef = ngProgress.ref();
progressRef.start();

• If you are using NgProgressRef to integrate it with other progress bar components

Before:

<ng-container *ngIf="progressRef.state$ | async; let state">
  <mat-progress-bar *ngIf="state.active" [value]="state.value"></mat-progress-bar>
</ng-container>

After:

<ng-container *ngIf="progressRef.state | async; let state">
  <mat-progress-bar *ngIf="state.active" [value]="state.value"></mat-progress-bar>
</ng-container>

5.1.2

• fix(router): Progressbar is not completing when navigation ends, closes #202 in 6d8b644.
• fix(router): Fix router config.delay is undefined error, in 9dae94b.

5.1.0

• feat(http): Add optional config to set progressRef id and silent APIs, closes #83 in 3c1d72c (Thanks to @bboyz269).
• feat(router): Add optional config to set progressRef id and a delay to complete the progress bar, closes #181 in d274745.
• refactor(NgProgress): Use, {providedIn: 'root'} instead of useFactory function in d31cacd.

Breaking changes

Before, to add the automagic features, we used to import NgProgressHttpModule and NgProgressRouterModule.

Now we must use forRoot() on these modules => NgProgressHttpModule.forRoot() and NgProgressRouterModule.forRoot().

5.0.1

• fix(build): fix warning " > @ngx-progressbar/core@5.0.0" has incorrect peer dependency "@angular/core@5.0.0".

5.0.0

• fixbug(build): fix build aot failure with angular 6, closes #143, #167, #166, #165, #164, #163, #162, #161, #160