Topic: No longer able to install Pro version

pedrojrivera free asked 3 years ago

Up until today I was able to make new projects and import the Pro version using the quick start guide. I've done this at least 30+ times, then today I run into a brand new error when trying to run NPM Install after pointing the dependencies towards


Here are the errors being printed to the console.

$ npm install
npm ERR! path C:\Users\ME\Documents\Company\Learn\testing\testing\node_modules\ng-uikit-pro-standard
npm ERR! code EISGIT
npm ERR! git C:\Users\ME\Documents\Company\Learn\testing\testing\node_modules\ng-uikit-pro-standard: Appears to be a git repo or submodule.
npm ERR! git     C:\Users\ME\Documents\Company\Learn\testing\testing\node_modules\ng-uikit-pro-standard
npm ERR! git Refusing to remove it. Update manually,
npm ERR! git or move it out of the way first.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\ME\AppData\Roaming\npm-cache\_logs\2019-03-04T18_06_40_705Z-debug.log

These are brand new projects generated by angular CLI that I am testing on.

dvdfeherther free answered 3 years ago

@pedrojrivera I had the same issue.

My workaround is:

  • Remove node_modules\ng-uikit-pro-standard\.git from your project.

Damian Gemza staff answered 3 years ago

Dear Starrcompanies,

I'm unable to reproduce this problem with the latest 7.4.4 version of MDB Angular.

Could you please specify the reproduction steps?

There no .gitlab directory in the ng-uikit-pro-standard repository, so there shouldn't be such error.

Best Regards,


starrcompanies free answered 3 years ago

@Damian Gemza This is happening again


"ng-uikit-pro-standard": "git+",

Can you advise

Damian Gemza staff answered 3 years ago

Dear PavlaQ,

Did you installed the updated repository? Few peoples said, that this problem is resolved even with an existing .gitlab directory in the package.

I have removed the .gitlab directory and updated the master branch, so please check if your problem is resolved.

Best Regards,


PavlaQ pro answered 3 years ago

@Damian Gemza I have the same problem, folder .gitlab crashes my application. Please remove this very quickly because this is our blocker!

Damian Gemza staff answered 3 years ago

Dear Inelo,

the .gitlab folder shouldn't break your application. We'll remove it in the next version.

Best Regards,


Inelo pro answered 3 years ago

@Damian Gemza Hi, I still have forder .gitlab on my ng-uikit-pro-standard package. Probably you have to remove it from master branch.

Damian Gemza staff answered 3 years ago

Dear starrcompanies,

We don't need to provide the version branches, because on the GitLab you're able to install the package by using the version tag.

For example, if you want to install the 7.4.1 version of MDB Angular, add the #7.4.1 to the ng-uikit-pro-standard dependency in the package.json file.

Please take a look at the example dependency with specific version:

"ng-uikit-pro-standard": "git+",

Best Regards,


starrcompanies free answered 3 years ago

Please provide version branches that we can get, so that we can roll back when this stuff breaks, or so that we can manually update our version instead of relying on latest. We use CI/CD servers that don't store packages. I'd expect released versions to be stable.

Damian Gemza staff answered 3 years ago


I have managed a hotfix for this situation. It's available on the #dev branch of ng-uikit-pro-standard repository.

Please check, if your problem will be gone while using the ng-uikit-pro-standard package installed from #dev.

Remove the node_modules directory and package-lock.json file and then use the below command to install the #dev package:

npm install git+https://oauth2:<token> --save

Please let me know if this resolves your problem. If this hotfix will work, I'll merge it to the master branch.

Best Regards,


pedrojrivera free commented 3 years ago

That seemed to do the trick.

Made a new application using the angular CLI then ran the install path provided. Followed the rest of the normal steps (without removing the node_modules folder) with no errors.

starrcompanies free commented 3 years ago

Confirming this worked for us as well

starrcompanies free answered 3 years ago

This is blocking us as well. Our build process is now failing on npm install. Can you please provide a fix asap?

pedrojrivera free answered 3 years ago

@roman.dzhadan that did it! I tired removing .git from the entire file folder at first and was still getting the same error. Removed node_modules\ng-uikit-pro-standard\.git and it works great now.

@Damian All I did was follow the MDB Pro start up guide to the letter. The error would normally be thrown on step #6

Step 6: Install 3rd party libraries using
npm i --save chart.js@2.5.0 @types/chart.js easy-pie-chart@2.1.7 hammerjs@2.0.8 screenfull@3.3.0 @fortawesome/fontawesome-free

The error was thrown at this point because of the npm install. If at any time before this step I would run npm install for the fun of it I would get the same error. The problem seems to stem from the .git folder in the node_module only once I would point my ng-uikit-pro-standard dependency to the .git path outlined in the guide.

Damian Gemza staff answered 3 years ago

Dear pedro,

How can I reproduce your problem?

I have created a brand new angular app using ng new.

In this app, I have installed the ng-uikit-pro-standard latest version, and there was no such error.

Could you please provide me with the reproduction steps?

Best Regards,


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: Free
  • Premium support: No
  • Technology: MDB Angular
  • MDB Version: 7.4.1
  • Device: Desktop
  • Browser: Chrome
  • OS: Windows 10
  • Provided sample code: No
  • Provided link: No