You're in good company

Right off the bat get your own personal site - use it as a free personal blog, or portfolio site.

Free forever

Customize your site's branding - your own custom domain, colors, layout, and more.

Tailor your branding.

Home

Today I ran into a mystery issue with an 

After some back-and-forth it turned out it had little to do with the 

 package, and it was mostly related to some reference file in 

 that was referencing some old installation of 

 for years now, and after stepping away from it for a while, a new major version landed and as the major versions do, it introduced some breaking changes. So I needed to upgrade the package.

 ..., restarting my computer afterwards, nothing seemed to really remove the package, even though the 

 - everything seemed to be uninstalled correctly, yet I was able to run 

 and that returned an outdated version - 

So I started digging and it started to seem that it had nothing to do with 

, and everything to do with something else; long story short, here's what fixed it for me...

The solution that ultimately resolved my issue of that stale shadow installation of the 

You can ensure that the package is completely removed by running any command provided by the package; for example, I ran the above mentioned 

Once you've cleaned everything up, you can now if need be re-install a fresh, up-to-date version of the package.

Hope this saves you some time 🙌🏼💜

prisma

Removed npm package, but it's not removed? This just may save your day.

Completely uninstalling npm package

Comments