Topic: Problems installing the pinned version using npm
I have installed MDB Pro Essential via NPM and have the following in package.json within the devDepdencies section:
"mdb-ui-kit": "git+https://oauth2:myoauthkey@git.mdbootstrap.com/mdb/standard/mdb-ui-kit-pro-essential"
Whenever I do npm outdated, it always marks mdb-ui-kit as being outdated. Version installed is 3.5.1 for example right now, latest is git, wanted is git. A few moments ago when I was still on 3.5.0, I did npm update and it updated to the current version and package-lock.json was updated to have the following version for mdb-ui-kit: "git+https://oauth2:myoauthkey@git.mdbootstrap.com/mdb/standard/mdb-ui-kit-pro-essential#6163dd52313bbe88132595bb2b81fb73b5fe1241". Pushed the changes to the package-lock.json and had a team colleague pull the changes and do an npm install. We were baffled to see that the node_modules/mdb-ui-kit/README.txt still listed version 3.2.0 on his machine, so npm install apparently has trouble updating.
Anyone else experiencing this issue? Is this an npm bug? Am I doing something wrong?
All files should be updated. readme.txt as well. Otherwise, I suggest you reinstall mdb-ui-kit to make sure you are running the latest version. Due to how mdb-ui-kit is installed, the npm update command will show our package as outdated. Adding #3.5.1 to package.json should actually fix this problem.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- User: Pro
- Premium support: Yes
- Technology: MDB Standard
- MDB Version: MDB5 3.5.1
- Device: PC
- Browser: Does not apply
- OS: Linux
- Provided sample code: No
- Provided link: No
UNNdev pro premium priority commented 4 years ago
I came around the problem by also adding
#3.5.1topackage.json.