I recently purchased the Material Design with Bootstrap for Angular. I've been wrestling with my Mac trying to get it installed over the last few days, mainly permission issues.... The support guys over there are very cool and have been dealing with my beginner issues, but I think something else may be up with my system.... Whenever I run their install command from within my project, for example: sudo npm install git+ --save I get a lengthy result but in it is always this problem: ...
gyp verb get node dir target node version installed: 8.9.4

gyp verb build dir attempting to create "build" dir: /Users/rich/Desktop/angular02/node_modules/node-sass/build

gyp ERR! configure error 

gyp ERR! stack Error: EACCES: permission denied, mkdir '/Users/rich/Desktop/angular02/node_modules/node-sass/build'

gyp ERR! System Darwin 15.6.0
... But here's the problem: the error message says permission denied for the mkdir command on the directory, so I simply went and set the permissions on my project folder (and all enclosed items) to access for everyone (I actually did this right after I created the Angular project "ng new myProjectName --style-scss"). But the error still keeps coming and the install fails, and even running ng serve fails (complains it can't find module node-sass, which is what's being blocked from being created).  What else can I do besides manually setting my project folder's permissions to make this installation work?  Yes, I've uninstalled, reinstalled Node/CLI/Angular.... I've run everything as sudo.... BTW I also get a similar issue when trying to install the Free version (I've been trying to install the Pro) Thanks, Rich My configuration:
Angular CLI: 1.5.0

Node: 8.9.4

OS: darwin x64

Angular: 5.2.0

... animations, common, compiler, compiler-cli, core, forms

... http, language-service, platform-browser

... platform-browser-dynamic, router

@angular/cli: 1.5.0

@angular-devkit/build-optimizer: 0.0.36

@angular-devkit/core: 0.0.22

@angular-devkit/schematics: 0.0.42

@ngtools/json-schema: 1.1.0

@ngtools/webpack: 1.8.0

@schematics/angular: 0.1.11

@schematics/schematics: 0.0.11

typescript: 2.5.3

webpack: 3.10.0

Dawid Adach pro answered 4 years ago

Dear Rich, Damian has offered you a support steps since few days. I have also replied to your email on January 9th including solutions steps. The issue which you are facing is anyhow related to our library. There is something wrong with your environment and until you solve that there is not much we can do as this exceeds scope of our support. MDB cannot modify access level to the files nor directories on your machine. This i technically impossible, otherwise it would be a huge security gap and anyone could publish repository to npm, and during installation change ownership to all system files of the client. This is something which operating system layer prevents from happening. If you cannot fix your environment as Damian advised (reinstallation of npm/angular globally using correct user) please try to setup on other machines preferably with the different operating system to exclude option that there is something wrong with the current setup. You could also create a virtual machine with i.e. fresh Ubuntu installation and install MDB there to verify that it works. Please try to execute it and let us know what the outcomes are. Until then we cannot provide you any other support nor refund as all the issues are NOT related to MDB itself. Here you can find detailed guide: pro answered 4 years ago

Guys this didn't work. It says the directory doesn't even exist. I've asked you for a support call and you won't do anymore than repeat instructions from articles that I supply to you. Please process my refund. And in the future kindly clarify the level of support that you actually offer.

Damian Gemza staff answered 4 years ago

Rich, i've read your's link. I have few solutions for you that can help solve problem.

First - Try to do something like this:

I run chown it's worked
sudo chown -r XXX /usr/lib/node_modules/ or sudo chown -r XXX /usr/lib/node_modules/@angular/
if not it might chgrp
sudo chgrp -r XXX /usr/lib/node_modules/


If not, please try this:

1.) Fix the permissions by changing the ownership and group of /usr/lib/node_modules/ to your user account: sudo chown -r XXX /usr/lib/node_modules/ and sudo chgrp -r XXX /usr/lib/node_modules/ 2.) sudo npm i -g @angular/cli 3.) sudo rm -fr /usr/lib/node_modules/@angular/cli/ 4.) sudo chown -r XXX /usr/lib/node_modules/@angular/ 5.) sudo chgrp -r XXX /usr/lib/node_modules/@angular/ 6.) npm i -g @angular/cli

If second method won't help you too, last thing is you to read carefully these two links: and

This should fix your's problem if you will do everything in right way :) GOOD LUCK!

Best Regards,

Damian pro answered 4 years ago

Hey Guys I found this, could this be relevant? I'm not exactly sure how I would implement this to immediately address the concerns I've been having with your installer, could you take a look?   Rich

Please insert min. 20 characters.


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



Specification of the issue

  • User: Pro
  • Premium support: No
  • Technology: MDB Angular
  • MDB Version: -
  • Device: -
  • Browser: -
  • OS: -
  • Provided sample code: No
  • Provided link: Yes