Getting meteor 0.9.2 for OSX & # 8594; Linux

Question

I used meteor 0.8.x, but recently tried to upgrade to 0.9.2. It works locally, but I had no luck with meteor bundle or meteor build

I got this error first

 /var/projects/myproject/live/bundle/programs/server/boot.js:198 }).run(); ^ Error: /var/projects/myproject/live/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) at require (module.js:380:17) at bindings (/var/projects/myproject/live/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15) at Object.<anonymous> (/var/projects/myproject/live/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/bcrypt.js:1:97) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) 

Things i tried

• Make sure that live/bundle/programs/server/node_modules does not exist before starting.
• ran npm install in live/bundle/programs/server since README says

Things I noticed. There bcrypt is located in live/bundle/programs/server/package.json . In 0.8.2, I had commands to install both fibers and bcrypt manually, but apparently I no longer need fibers. It looks like I need bcrypt alone, but it's in a different place than before.

I don’t see anything in the documents about the need to go to /var/projects/myproject/live/bundle/programs/server/npm/npm-bcrypt and install bcrypt . I can delete it manually, but am doing something wrong?

As I said, I already install it where 0.8.2 needed it in programs/server . Should I manually install in program/server/npm/npm-bcrypt ? Should I add this to my list of places to ignore

I put it just to try and now I get this error

 /var/projects/myproject/live/bundle/programs/server/node_modules/fibers/future.js:173 throw(ex); ^ Error: Cannot find module 'websocket-driver' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/var/projects/myproject/live/bundle/programs/server/npm/ddp/node_modules/faye-websocket/lib/faye/websocket.js:8:14) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) 

Is this another module that I need to install manually? I get the impression that I'm just doing something fundamentally wrong.

I have the following meteor packets

.meteor / packages

 # Meteor packages used by this project, one per line. # # 'meteor add' and 'meteor remove' will edit this file for you, # but you can also edit it by hand. standard-app-packages audit-argument-checks iron: router@0.9.3 meteorhacks: npm@1.2.0 npm-container 

packages.json

 { "semver": "2.3.1", "winston": "0.7.3", "winston-loggly": "1.0.1" } 

note: I am developing / integrating OSX but deploying to Ubuntu.

Answer 1

I had similar problems - I sent my solution to DO

https://www.digitalocean.com/community/tutorials/how-to-deploy-a-meteor-js-application-on-ubuntu-14-04-with-nginx?comment=19780

---

UPDATE - here is the answer from this forum:

If anyone else has a problem with bcrypt, the application probably has its own copy in /home/yourapp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/

remove this noise. Then do it.

cd /home/yourapp/bundle/programs/server

npm install bcrypt

Then

cp -r /home/yourapp/bundle/programs/server/node_modules/bcrypt /home/yourapp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/

then launch your app and enjoy the goodness of meteory.

Answer 2

About the general problem.,.

(for those who stumble here through Google)

Unable to find module 'MODULE-NAME'

or

Unable to find npm module 'MODULE-NAME'

If you recently added or removed packages while the application is running, try stopping and restarting the meteorite application.

 // stop ( "CTRL+C" in terminal that launched process ) $ kill `ps ax | grep '[m]eteor' | awk '{print $1}'` // start $ meteor