v0.3.0-beta.20

• feat: @authenticated directive (#366)
• graphql remove the email key on the user and the CreateUserProfileInput type (#365)
• Feature/improve graphql gen types (#364)

Breaking changes

• removed the email key on the User type and the CreateUserProfileInput type, see README to know how to extend the CreateUser type.
• renamed createJSAccountsGraphQL to createAccountsGraphQL
• renamed JSAccountsContext to accountsContext
• removed the extendWithResolvers export, see README to know how to merge with your resolvers.

v0.3.0-beta.19

• fix graphql-api package (#363)

v0.3.0-beta.18

We had to switch from 0.1.0.betaX to 0.3.0.betaX because the graphql packages were published as 0.2.X versions

• graphql support 🎉 huge thanks to @rankun203 #361
  • client instructions: https://github.com/accounts-js/accounts/tree/master/packages/graphql-client
  • server instructions https://github.com/accounts-js/accounts/tree/master/packages/graphql-api
• Fix rest-express impersonate call #359

v0.1.0-beta.17

• return tokens from loginWithService (#347)
• Feature/upgrade deps (#350)
• warm user in case of default token (#351)
• When verifying email test the token is not expired (#352)
• noUnusedLocals (#353)
• Feature/better typings (#356)
• feat: exporting all types inside @accounts/password (#358)

Support for SSR

Additions

• #324: Thanks to @kamilkisiela for adding in express-session package. This allows for authenticated SSR.
• #345: Feature/remove common package.
• #344: Pass the params and error to the login hooks.

Fixes

• #346: Upgrade to typescript 2.9.1 and emittery 0.4.0 to fix breaking build on updated TS apps.

v0.1.0-beta.14

Something went wrong when publishing v0.1.0-beta.13

v0.1.0-beta.13

• @accounts/client refactor and @accounts-password created #316

Usage:

const accountsClient = new AccountsClient({ ...options }, transport);
const accountsPassword = new AccountsClientPassword(accountsClient, { ...options });

The user should now use the client-password.createUser function that will encrypt the user password before sending it to the server.

The user should now use the client-password.login function that will encrypt the user password before sending it to the server.

By default we will only hash the password with the SHA256 algorithm. And there is an option for the user to define the method of his choice, in that way we do not import the whole crypto-js library which is pretty big.

Breaking changes

• accounts-client.tokens() is now accounts-client.getTokens()
• if you used accounts-client.createUser() you can now use accounts-password.createUser()
• For the users created before this version you will not be able to use the client-password.login that will encrypt the user password before sending it to the server.
  There is two workaround:
  • continue to use the client.loginWithService method which does not encrypt the password.
  • inside client-password provide the hashPassword function that will just return the string in plain text for example:

const accountsPassword = new AccountsClientPassword(accountsClient, {
  hashPassword: (password) => password
});

v0.1.0-beta.12

• Pass some context to the login hooks (#317)
  The ServerHooks.LoginSuccess and ServerHooks.LoginError now receive the following infos:

{
  // The service name, such as “password” or “twitter”.
  service: string
  // The connection informations <ConnectionInformations>
  connection
  // The user object if set
  user
}

• Feature/database redis sessions store (#323) see https://github.com/accounts-js/accounts/blob/master/packages/database-redis/README.md for docs
• Add prettier commit hook (#332)
• The tests should fail if non prettied files are commited (#338)
• Only refresh the tokens if refresh token is not expired on the client (#339)

Breaking changes

• The server hooks key Login has been renamed to ValidateLogin
• The server loginWithUser function does not trigger the login hooks anymore

v0.1.0-beta.11

• New database-manager package: Allow sessions and users to be stored in different databases #174
• Create a changePassword function that can be used when user is logged in #312
• We now use yarn workspaces with lerna #313
• The user's email will be verified after clicking on the enrolment link #315
• No longer set profile data in OAuth #331