Holiday Notice: Support will be provided on a limited scale from December 24th, 2024, to January 2nd, 2025. Happy holidays and a wonderful New Year!


Topic: Issues After Upgrade

taylorc67 pro asked 5 years ago


Issues after upgrade to 8.1.1 After upgrading MDB Bootstrap I am getting the following errors:

vendor.js:140303 ./node_modules/ng-uikit-pro-standard/fesm5/ng-uikit-pro-standard.js 10466:57-75 "export 'ɵɵdefineInjectable' was not found in '@angular/core'

I have tried this with Angular 7.0 and Angular 8.0

Any idea what might be wrong?


Arkadiusz Idzikowski staff commented 5 years ago

Could you paste here the content of your package.json file? Please remember to remove your private MDB gitlab token if you use one there.


taylorc67 pro commented 5 years ago

Here you go:

{ "name": "designer-hub", "version": "0.0.0", "scripts": { "ng": "ng", "start": "ng serve", "build": "ng build", "test": "ng test", "lint": "ng lint", "e2e": "ng e2e" }, "private": true, "dependencies": { "@angular/animations": "~8.2.0", "@angular/common": "~8.2.0", "@angular/compiler": "~8.2.0", "@angular/core": "~8.2.0", "@angular/forms": "~8.2.0", "@angular/platform-browser": "~8.2.0", "@angular/platform-browser-dynamic": "~8.2.0", "@angular/router": "~8.2.0", "@fortawesome/fontawesome-free": "^5.10.1", "@types/chart.js": "^2.8.1", "animate.css": "^3.7.2", "chart.js": "^2.5.0", "core-js": "^2.5.4", "dotenv": "^6.2.0", "easy-pie-chart": "^2.1.7", "hammerjs": "^2.0.8", "libphonenumber-js": "^1.7.8", "ng-recaptcha": "^4.2.1", "ng-uikit-pro-standard": "git+https://oauth2:@git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git", "rxjs": "~6.4.0", "screenfull": "^3.3.0", "tslib": "^1.10.0", "yargs": "^13.2.1", "zone.js": "~0.9.1" }, "devDependencies": { "@angular-devkit/build-angular": "~0.802.2", "@angular/cli": "~8.2.2", "@angular/compiler-cli": "~8.2.0", "@angular/language-service": "~8.2.0", "@types/node": "~8.9.4", "@types/jasmine": "~3.3.8", "@types/jasminewd2": "~2.0.3", "codelyzer": "^5.0.0", "jasmine-core": "~3.4.0", "jasmine-spec-reporter": "~4.2.1", "karma": "~4.1.0", "karma-chrome-launcher": "~2.2.0", "karma-coverage-istanbul-reporter": "~2.0.1", "karma-jasmine": "~2.0.1", "karma-jasmine-html-reporter": "^1.4.0", "protractor": "~5.4.0", "ts-node": "~7.0.0", "tslint": "~5.15.0", "typescript": "~3.5.3" } }


Arkadiusz Idzikowski staff commented 5 years ago

Please try to remove your node_modules folder and package-lock.json file and run npm install command again. This error often occur when someone try to use MDB 8 with Angular 7, but the packages versions looks good in this case.


taylorc67 pro commented 5 years ago

I had tried that but tried it again. After fighting some node-sass issues I am able to ng serve but nothing is rendering and I still see the following message:

WARNING in ./node_modules/ng-uikit-pro-standard/fesm5/ng-uikit-pro-standard.js 10466:57-75 "export 'ɵɵdefineInjectable' was not found in '@angular/core' ℹ 「wdm」: Compiled with warnings.


Arkadiusz Idzikowski staff commented 5 years ago

Please send a demo project on which I will be able to reproduce this problems to a.idzikowski@mdbootstrap.com. I'd like to check the configuration files.


taylorc67 pro answered 5 years ago


We can table this for the time being. I think I am just going to start with a fresh project targeting Angular 8 that uses MDB Angular 8.1.1 and add in my existing pages to try and pinpoint the problem. When I start up a new project, there does not appear to be an issue.

I don't have a ready demo project to upload, so I will just let you know if I run into the issue at some point with one of my existing pages in the new app.


taylorc67 pro commented 5 years ago

After starting a new project and then copying all objects over from my old project, I am back up and running. I am not sure what happened, but something got messed up by my upgrade. Hopefully it does not happen again the next time...


Arkadiusz Idzikowski staff commented 5 years ago

Glad it works. It's hard to the tell what exactly happened there, but it look like you were using MDB Angular 8 with Angular 7. Maybe it was problem with npm cache.


taylorc67 pro commented 5 years ago

That is possible. I grabbed the package.json from my migrated project and replaced it for the original project and it is working fine now too.

I suspect it was 'operator error' in this case.

Thanks for your help.



Please insert min. 20 characters.

FREE CONSULTATION

Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.

Status

Resolved

Specification of the issue

  • ForumUser: Pro
  • Premium support: No
  • Technology: MDB Angular
  • MDB Version: 8.1.1
  • Device: Browser
  • Browser: Chrome
  • OS: Windows 10
  • Provided sample code: No
  • Provided link: No