Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade to angular9 occurs error #355

Open
crystalYY opened this issue Feb 28, 2020 · 3 comments
Open

upgrade to angular9 occurs error #355

crystalYY opened this issue Feb 28, 2020 · 3 comments

Comments

@crystalYY
Copy link

version:
"dependencies": {
"@angular/animations": "^9.0.2",
"@angular/cdk": "^9.1.0",
"@angular/common": "^9.0.2",
"@angular/compiler": "^9.0.2",
"@angular/core": "^9.0.2",
"@angular/flex-layout": "^9.0.0-beta.29",
"@angular/forms": "^9.0.2",
"@angular/localize": "^9.0.3",
"@angular/platform-browser": "^9.0.2",
"@angular/platform-browser-dynamic": "^9.0.2",
"@angular/router": "^9.0.2",
"@ng-bootstrap/ng-bootstrap": "^6.0.0",
"angularx-qrcode": "^2.1.0",
"core-js": "^3.6.4",
"ng2-datepicker": "^3.1.1",
"pdfjs-dist": "^2.0.489",
"punycode": "^2.1.1",
"rxjs": "^6.5.4",
"tslib": "^1.11.0",
"zone.js": "~0.10.2"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.900.3",
"@angular/cli": "^9.0.3",
"@angular/compiler-cli": "^9.0.2",
"@angular/language-service": "^9.0.2",
"@angular/service-worker": "^9.0.2",
"@types/jasmine": "~3.5.7",
"@types/jasminewd2": "~2.0.8",
"@types/node": "^13.7.6",
"@types/pdfjs-dist": "^2.1.3",
"codelyzer": "^5.2.1",
"jasmine-core": "~3.5.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~4.4.1",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage-istanbul-reporter": "^2.1.1",
"karma-jasmine": "~3.1.1",
"karma-jasmine-html-reporter": "^1.5.2",
"pdfjs-dist": "^2.0.489",
"protractor": "~5.4.3",
"replace-in-file": "^5.0.2",
"ts-node": "~8.6.2",
"tslint": "^5.20.1",
"typescript": "~3.6.2"
}
error:
when compile ,I got this error

ERROR in node_modules/ng2-datepicker/dist/src/ng-datepicker/module/ng-datepicker.module.d.ts:1:22 - error NG6002: Appears in the NgModule.imports of ComponentsModule, but could not be resolved to an NgModule class.
    
    This likely means that the library (ng2-datepicker) which declares NgDatepickerModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
    
    1 export declare class NgDatepickerModule {
                           ~~~~~~~~~~~~~~~~~~
    node_modules/ng2-datepicker/dist/src/ng-datepicker/module/ng-datepicker.module.d.ts:1:22 - error NG6003: Appears in the NgModule.exports of ComponentsModule, but could not be resolved to an NgModule, Component, Directive, or Pipe class.
    
    This likely means that the library (ng2-datepicker) which declares NgDatepickerModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
    
    1 export declare class NgDatepickerModule {
                           ~~~~~~~~~~~~~~~~~~
    src/app/shared/components/components.module.ts:279:14 - error NG6002: Appears in the NgModule.imports of HomeModuleModule, but itself has errors
    
    279 export class ComponentsModule { }
                     ~~~~~~~~~~~~~~~~
    src/app/shared/components/components.module.ts:279:14 - error NG6002: Appears in the NgModule.imports of AppModule, but itself has errors
    
    279 export class ComponentsModule { }
                     ~~~~~~~~~~~~~~~~
    src/app/home/home.module.ts:83:14 - error NG6002: Appears in the NgModule.imports of AppModule, but itself has errors
    
    83 export class HomeModuleModule { }
                    ~~~~~~~~~~~~~~~~
@adiagrwl94
Copy link

@crystalYY Any resolution or workarounds?

@crystalYY
Copy link
Author

@crystalYY Any resolution or workarounds?

not yet

@ethyaan
Copy link

ethyaan commented Jul 16, 2020

So is there any plan at least?
this project is not updated over two years.
many issues and many pending pull-request.
I can fix this but why should I wait for this fix to get applied?
Since this is breaking my whole pipe line.
I prefer to use other alternatives.
lets never fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants