Local package is not being used, despite METEOR_PACKAGE_DIRS being set correctly

1

I only just started having this problem—the local version of one of my packages has some small but critical changes, and meteor is now for some reason not picking it up. I can tell by 1) meteor list does not show that it is using the local version with the + sign and 2) console.logs that I add locally are not occurring.

I have verified that METEOR_PACKAGE_DIRS is set correctly, and I have been doing this for a while with no problems… what else am I missing?

—T3db0t
http://grooply.io

2

It’s PACKAGE_DIRS not METEOR_PACKAGE_DIRS.

3

As of one of the most recent versions, PACKAGE_DIRS was officially deprecated in favor of METEOR_PACKAGE_DIRS (see here), though for some reason this is not in any of the release notes.

Regardless, I have both set and none of my local packages are being recognized/used.

1 Like
4

Sigh, nevermind, it turned out I hadn’t exported the env variable, though I thought I had.

1 Like
5

Oh, didn’t know that. Thanks for the info. Glad you could solve your problem :thumbsup: