Somewhere between version 1.3 and 1.4 of meteor I had to install a specific version of bcrypt because of some accounts-ui issue - I’ve since lost track of that github issue so I’m having trouble going back over what I’ve changed. Now I keep getting this error: W20160830-11:50:40.866(-4)? (STDERR) …

This is driving me nuts… I tried the above remedies, none of which fixed it. Now it complains every time I run meteor, even after issuing the command to install bcrypt npm rebuild didn’t help. Trying to remove node-bcrypt didn’t work, Meteor just put it back in there. Can someone please provide a…

Same issue on Windows and Mac. Tried the solutions above on Mac, minus the windows specific build part. Still get the full list of errors. And yes, it is very annoying to see those warnings int he terminal when you start meteor.

I’m on Mac, rebuild works for me. Remove bcrypt from package.json and .meteor/package, then do meteor npm install --save bcrypt meteor npm rebuild Hooray, no more warnings!

Solved this (what a hell). This works: meteor add npm-bcrypt meteor add accounts-password this doesn’t: meteor npm install bcrypt meteor add accounts-password

Incredible how far Meteor has fallen. Cant even add basic user authentication without running into a ton of issues with no clear fix. I came to Meteor for the simplicity, it’s simply horrendous how MDG has butchered and treated their product.

This is one issue which is easily solved.

The best explanation for El Capitan+ El Capitan’s new System Integrity Protection feature prevents changes to several core parts of OS X, including most of /usr, even by root. Local customizations, such as what you’re doing, belong in /usr/local instead. /usr/local/bin doesn’t exist by default, bu…

Yep, this is so sad… moving to arunoda stack

Meteor Forum

Npm bcrypt and meteor npm bcrypt madness

help

samahudin November 6, 2016, 11:29am 24

Try this.