ng serve stops working for ngx-webstorage-service in 0.800.4 (worked in 0.800.3)

[qortex]

🐞 Bug report

Command

- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Regression

Works in 0.800.3, breaks in 0.800.4

Description

ng build works fine on my project (and still does).

ng serve worked fine until @angular-devkit/build-angular - 0.800.4, now it breaks with the message below. Works ok if I downgrade @angular-devkit/build-angular to 0.800.3.

The package is: https://github.com/dscheerens/ngx-webstorage-service

The place where the class is exported is: https://github.com/dscheerens/ngx-webstorage-service/blob/master/lib/src/storage.service.ts

Maybe there is an issue because the class is a generic type?

🔥 Exception or Error

ERROR in ./src/app/services/my.service.ts 84:12-26
"export 'StorageService' was not found in 'ngx-webstorage-service'
ERROR in ./src/app/services/my.service.ts 85:12-26
"export 'StorageService' was not found in 'ngx-webstorage-service'

🌍 Your Environment

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.4
@angular-devkit/build-angular     0.800.4
@angular-devkit/build-optimizer   0.800.4
@angular-devkit/build-webpack     0.800.4
@angular-devkit/core              8.0.4
@angular-devkit/schematics        8.0.4
@angular/cdk                      8.0.1
@angular/cli                      8.0.4
@angular/flex-layout              8.0.0-beta.26
@angular/material                 8.0.1
@ngtools/webpack                  8.0.4
@schematics/angular               8.0.4
@schematics/update                0.800.4
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.30.0

Other

Tracked on the package repo: dscheerens/ngx-webstorage-service#11

[qortex]

Ho oups
Actually, same as this issue: #14876

Closing this one.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}