Terry Appleby

Thanks for bringing this up, I didnt know you could skip the pre-flight options request w/ CORS. I will look into adding support for the Auth header over next few...

Thanks for the feedback, glad its useful! OAuth can be a pain for basic stuff which is why I originally wrote this library. I actually also have a laravel oauth2...

Yeah I created the feature/jwt branch when that auth0 blog post was first posted. Not much progress was made with it, there was not many options for php JWT at...

Yeah you would need to load the relations in `auth.token.valid` (Or perhaps another part of your application eg: controller or route filter). The `auth.token.created` is only fired in the `AuthTokenController::store`...

If you setup the [optional aliases](https://github.com/tappleby/laravel-auth-token#setup), you can use the facade: `AuthToken::validate($token)`

@PadreMontoya any luck with using the facade? let me know if your still running into issues.

Yeah im not sure what the compatibility would be like, its possible it could just work (I dont know enough about Neo4J). You could supply your own Neo4J provider based...

I am postponing the merge of #27. I need to revisit the Controller and don't wont to introduce a change that might be short-lived.

I created a recent PR #29 which is a more complete update for React 14. It is not backwards compatible with v13 though. I also have a scoped version published...

Looking into getting this PR merged soon. Just evaluating the impact future redux store enhancer api changes might have on this: - https://github.com/reactjs/redux/pull/1702 - https://github.com/reactjs/redux/pull/2214#discussion_r98359849