I was watching a screencast about Meteor 's user account system, and the author of the video used the accounts-base package , in addition to accounts-password, accounts-ui, and accounts-twitter.
I knew about those packages, except for accounts-base . I understand that accounts-ui is what gives you the login window, if you don't want to build your own login screens. Accounts-password lets you create user accounts and you can parameterize the data that will be needed for login with something like:
Accounts.ui.config({
//passwordSignupFields: "USERNAME_ONLY"
passwordSignupFields: 'USERNAME_AND_EMAIL'
});
and accounts-twitter (or accounts-google, etc. ) to configure access through a twitter, google, weibo, github...
I see that account-ui, accounts-password, and in general accounts-XYZ depend on this package, but it's not clear to me what functionality this package has per se. I mean, I don't know what would justify meteor add accounts-base
inadvertently adding accounts-password. I don't know if I get all of its functionality by default when doing a meteor add accounts-password
, for example.
Does the accounts-base package have anything that isn't already in the other user account packages in Meteor?
Note: the video is quite old, and at times uses things like Meteor.autosubscribe
, which I know has already been deprecated in favor of Deps.autorun
or Tracker.autorun
. I don't know if at some point it was necessary to add this basic package and then its functionality was incorporated in others.