Topic: File to import not found or unreadable: core/bootstrap/functions.
We are upgrading to version 7.4.0 and i am getting the following error on ng serve.
File to import not found or unreadable: core/bootstrap/functions. in /Users/.../.../.../node_modules/ng-uikit-pro-standard/assets/scss/mdb.scss (line 31, column 1)
If i look in node_modules/ng-uikit-pro-standard/assets/scss/ folder, the core folder is missing. We are using the git method on this url:
git+https://oauth2:xxxxx@git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git#7.4.0
Did many reinstalls, but the core folder just is not copied for some reason.
How can we fix this?
Yes, you can also:
- Removed the node_modules directory
- Downgraded your npm to 6.4.1 version
- Run npm install
- Updated your npm to last npm version (6.8.0) sudo npm -g update npm or a command like that...
- Everything should work correctly...
I solved it through a workaround:
I downloaded the project from gthub https://git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard and copy "core" folder (ng-uikit-pro-standard-master\assets\scss\core) in node_modules folder of my project (\node_modules\ng-uikit-pro-standard\assets\scss).
Actually I'm using npm 6.8.0
I deleted my whole node_modules folder and ran npm install then npm install typescript@">=3.1.1 <3.3.0" and it works for me now.
Angular CLI: 7.0.4
Node: 10.15.1
Hello, The problem seems to appear when we are using the npm install command with the 6.8.0 npm version. With npm 6.4.1, everything seems to work properly.
I also faced this issue with clean install of 7.4.0
The problem is core folder is missing from that location.
I fixed it by placing core folder there from older version 7.3.0.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- ForumUser: Pro
- Premium support: No
- Technology: MDB Angular
- MDB Version: 7.0.0
- Device: macbook pro
- Browser: Chrome
- OS: macOS Mojave v10.14.3
- Provided sample code: No
- Provided link: Yes
ADS@Aareon pro commented 5 years ago
After a fun day of investigating this issue, i managed to get it running bij reverting to an old version of node/npn.
Now on node v8.15.0 npn v6.4.1
A bit of a hack/workaround, but it works for now.
@MDB Team: might want to look into this.Not sure if the problem is node/npm or the MDB package