DEV Community

Cover image for 🤦‍♂️ Weekly fail (38/2020)
Ilesh Mistry for Kontent.ai

Posted on

3 1

🤦‍♂️ 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.

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

Top comments (0)

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs