I’m sure there’s a simple answer for this, but I can’t think of it or seem to find it online at the moment:
I’ve forked a couple of Github repos for Atmosphere packages and I’ve got them installed locally with some tweaks. They do what I need them to do for a specific app’s use case, but now I would like to use the original Atmosphere hosted version of the package(s) to add to a fresh app with a different use case.
How do I ensure that
meteor add package:name will grab the Atmosphere-hosted version and not my local version? Is there a way to tell the
meteor add command to not look at the path associated with
METEOR_PACKAGE_DIRS in my .bash_profile, and go straight to Atmosphere to get the package instead?