Missing non-core packages when running meteor from checkout [SOLVED]


#1

When you are running meteorjs from git checkout there are some non-core packages which are not linked by default. This is described at: https://github.com/meteor/meteor/tree/devel/packages/non-core

To use these packages just have some options described in following. In case of meteor universal fork installation, I am thinking about to export PACKAGE_DIRS directly inside meteor starter.

Do you think this is a good decision to prevent some frustrations or will this break MDG policies?

Thanks for your hints.
Tom


Reference:

  1. https://github.com/4commerce-technologies-AG/meteor/issues/10
  2. https://github.com/4commerce-technologies-AG/meteor/issues/1
  3. https://github.com/meteor/meteor/tree/devel/packages/non-core

#3

Thanks to David ( @glasser ) for a clarification on github comment about using non-core packages.

So the advise is:

# setting the env var 
export PACKAGE_DIRS=<your meteor checkout path>/packages/non-core

If this is not suitable for you, you still may link the non-core package to your project

cd <your meteor app path>/packages
ln -s <your meteor checkout path>/non-core/npm-bcrypt .

Cheers