Should I install Supabase as a dev dependency with NPM or globally using Brew/Scoop?

[SpinningGalaxy]

I’m trying to decide on the best approach for integrating Supabase into my development setup. I’ve noticed two different methods being used, and I’m unsure which is the superior option.

One method is to install it as a dev dependency via NPM for each project. The alternative is to perform a global installation with package managers like Brew for Mac or Scoop for Windows.

NPM method:

npm install --save-dev supabase

Global method:

brew install supabase/tap/supabase
# or
scoop bucket add supabase https://github.com/supabase/scoop-bucket.git
scoop install supabase

What are the benefits and drawbacks of these approaches? I want to ensure that I’m adopting the best practices for my team’s development setup. Any insights would be greatly appreciated!

[John_Clever]

I’ve utilized the NPM dev dependency approach for two years and it has greatly minimized potential issues. The key advantage is maintaining version consistency; when a team member clones your repository, they get the exact version of the Supabase CLI you’re using. This prevents common ‘it works on my machine’ issues. In contrast, global installations can lead to version drift as different team members may update at varying times. I learned the drawbacks the hard way when our CI/CD pipeline failed due to a version mismatch. With NPM, the package.json file ensures everyone is synchronized, and the minor overhead for each project is negligible compared to the debugging time saved.

[miat]

I’ve used both methods across tons of projects. Your workflow really drives the choice here. Global Brew install is great when you’re jumping between different Supabase projects or just prototyping stuff quickly. No need to type npx every time, which speeds things up. But I ran into problems with legacy projects that needed older CLI versions - global install made managing multiple versions a nightmare. The NPM dev dependency adds extra steps but keeps everything isolated. My compromise? I use global for personal projects and stick with dev dependencies for team work where everyone needs the same version.

[CreatingStone]

i prefer global installs with brew too, it’s more convenient for managing space, plus you don’t gotta worry 'bout mismatched versions across projects. just chat with your teammates when updates are due to avoid surprises!