-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with everyauth after 0.3 version update #116
Comments
Same problem in my case:
|
Same here. |
same here @nleush i tried your I was able to resolve it by forcing an upgrade to mongoose 3.x all around. I also forked mongoose-auth here: https://github.com/davisford/mongoose-auth and I forced it to mongoose 3.x. In my project, I also depend on mongoose, so I forced that to 3.x and all seems to be working again. Here's the commit on my project -- you can inspect the complete npm-shrinkwrap to see if it helps resolve your deps. davisford/daisycentral@053be0b |
In my case the problem's cause was in Everyauth - see Issue 322, where the new Express autodetection functionality is put to blame. I've submitted pull request 323 to revert this functionality since it seems to be inherently broken to me. |
Is there any recent news on this issue? |
In my case, we've migrated to PassportJS since:
|
there seems to be some activity 20 days ago: https://github.com/bnoguchi/everyauth/tree/express3. @aadamowski Is there a comparable persistence module for Passport? |
AFAIR we've implemented a custom module analogous to Mongoose-auth. It wasn't exactly rocket science. |
TypeError: Object # has no method 'User'
at module.exports.findUserById (/node_modules/mongoose-auth/lib/modules/everymodule/everyauth.js:7:10)
Temporary fix available with package.json:
"dependencies": {
"mongoose-auth": "git://github.com/nleush/mongoose-auth.git",
}
The text was updated successfully, but these errors were encountered: