DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 964,423 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Cover image for πŸ€¦β€β™‚οΈ Weekly fail (38/2020)
Ilesh Mistry for Kontent.ai

Posted on

πŸ€¦β€β™‚οΈ Weekly fail (38/2020)

So I ran into a problem. I was getting numerous errors when trying to build my front end project. They had occurred from node modules either being outdated or dependencies not being there and as I was following different articles describing how to solve them, I soon had been installing plugins from 2 different package managers, NPM and Yarn.

As a result of this, I was getting lots of issues. It confused the hell out of me, but I then looked into my source files and noticed .lock file for both package managers. Oops!

So I resolved this by picking a specific package manager and sticking with it. I cleared out my Node Modules folder and removed the .lock files and reinstalled all the node modules (via npm install or yarn) and the errors didn’t persist :)

Lesson learned: Stick with one package manager. Always. I'm telling you.

Oldest comments (0)

DEV has this feature:

Settings

Go to your customization settings to nudge your home feed to show content more relevant to your developer experience level. πŸ›