File to import not found or unreadable: core/bootstrap/funct

Topic: File to import not found or unreadable: core/bootstrap/functions.

ADS@Aareon pro asked a year ago

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:


Did many reinstalls, but the core folder just is not copied for some reason.

How can we fix this?

ADS@Aareon pro commented a year 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

Thank you for all the information. We will check what may be the cause of this problem.

bitjuice pro answered a year ago

I solved it through a workaround:

I downloaded the project from gthub 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

deeep580 pro answered a year ago

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.

crounini pro answered a year ago

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.

elemech pro premium answered a year ago

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

crounini pro answered a year ago

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...

Damian Gemza staff answered a year ago

Yes, the workaround provided by the Crounini should work too.

Please insert min. 20 characters.


Specification of the issue
  • User: Pro
  • Premium support: No
  • Technology: Angular
  • MDB Version: 7.0.0
  • Device: macbook pro
  • Browser: Chrome
  • OS: macOS Mojave v10.14.3
  • Provided sample code: No
  • Provided link: Yes