Missing dependency npm-bcrypt when using accounts-password

[TPXP]

Hello!

First of all, many thanks for the hard work you put in this fork to support the ARM architecture, it's awesome!

I'm currently trying to create a project using accounts-password, so that users can connect with a password. But there's a little problem when running meteor add accounts-password, because a meteor package used to encrypt passwords : npm-bcrypt does not appear as compatible (you have to build it when you install it with npm) and meteor refuses to continue without this package.

As far as I could see (sorry I am not knowledgeable a lot about meteor internals 😕 ), this package is located at <meteor root>/packages/non-core/npm-bcrypt/. I tried installing the bcrypt package at <meteor root>/packages/non-core/npm-bcrypt/.npm/package/node_modules/bcrypt (note meteor wants version 0.7.7, not 0.8.0!), but still no luck, the package is not recognised as installed, so it tries to install it, and fails when I intent loading my project.

I also saw there was a node_modules in <meteor root>/dev-bundle/lib, but running npm install [email protected], once done, does not solve the problem.

Any idea how to fix this issue ?

Many thanks in advance!

[TomFreudenberg]

Hi, thanks for pointing that out here. Solution is very easy as you could read in

https://github.com/meteor/meteor/tree/devel/packages/non-core

To use these packages just have two options:

a. general: create a symbolic link into your meteors checkout

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

b. project specific

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

c. get published versions of the packages from Atmosphere

cd <your meteor app path>
meteor add npm-bcrypt

Personally I would prefer a.) to use always the git delivered versions

Tom

P.S.: There are maybe more non-core npm's. If you need to use it (e.g. npm-node-aes-gcm) go on with same procedere

[TomFreudenberg]

Issue documented and closed

[TPXP]

Many thanks for your help, I can confirm it works now! 👍

[TomFreudenberg]

ATTENTION !!! As from a comment from MDG you SHOULD NOT link the non-core packages directly inside the packages directoy of a checkout meteor.

The correct 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 .