Shared insights
on
npm
Yarn

#PackageManagers After a long time where npm failed to install packages and lot's of googling on answers, we switched to Yarn and alomost all those problems where solved. Today i mostly use "yarn add" instead of "npm install --save".

READ LESS
12 upvotes4 comments73.3K views
Avatar of undefined
Zoheb Akhtar
Zoheb Akhtar
December 30th 2018 at 9:57am

I have been having similar problems with npm on our dev machines ever since I started getting into the SharePoint Framework. Some things work with the new Node.JS version in one machine and the other times it fails. I'll try Yarn and see if it helps

Reply
Amir Aharon
Amir Aharon
December 31st 2018 at 8:00am

Yes, most of our problems with npm where from different version of node.js.

Reply
Adnan Fayaz
Adnan Fayaz
January 2nd 2019 at 6:13am

Switching to Yarn may be the right option, But you need to stick to that. Npm has alot of packages in it. NPM fails to install some of the packages because it has much dependencies. You should try to delete node_modules folder and package-lock.json file that creates an issue sometimes and re-install the packages.

Reply
alienfacepalm
alienfacepalm
January 6th 2019 at 11:10pm

React isn't a framework and Redux is mostly misused as client side views into a DB. Take a look at Apollo Kit by SysGears, a React-based boilerplate that uses Apollo which is far more powerful and correctly implemented. Redux is a joke.

Reply
Avatar of Amir Aharon