Skip to content

Angular 8 build contains ctorParameters #15404

Closed
@sam-s4s

Description

@sam-s4s

🐞 Bug report

Command (mark with an x)

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

Is this a regression?

Yes, the previous version in which this bug was not present was:

7.3.9

Description

I'm getting a lot of circular dependency warnings, and the app is not running after doing a dev build using ng build.
When doing a prod build using ng build --prod the build compiles and runs fine.
Also doing both types of builds worked perfectly in Angular 7, this problem has only started since I upgraded to Angular 8 yesterday.

🔥 Exception or Error


WARNING in Circular dependency detected:
a4\a4-action.ts -> a4\a4.service.ts -> a4\a4-action.ts

(above for example - there are about 50)

🌍 Your Environment


Angular CLI: 8.2.2
Node: 10.15.1
OS: win32 x64
Angular: 8.2.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.802.2
@angular-devkit/build-angular     0.802.2
@angular-devkit/build-optimizer   0.802.2
@angular-devkit/build-webpack     0.802.2
@angular-devkit/core              8.2.2
@angular-devkit/schematics        8.2.2
@ngtools/webpack                  8.2.2
@schematics/angular               8.2.2
@schematics/update                0.802.2
rxjs                              6.5.2
typescript                        3.5.3
webpack                           4.38.0

Anything else relevant?

I'm not sure why this problem has sprung up after an upgrade? It was working perfectly in Angular 7, and i haven't changed anything, other than running the upgrade to Angular 8.

I'm a bit stuck, as it's not easy to fix these problems, and there are about 50 of them - and as they weren't a problem before, I'm not sure why they would be now? Seems like a pretty massive regression?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions