Dan M.

@epilande, Just tested your proposed changes. Worked as expected, so I commited it to patch-1. Should be able to pull now.

(also took a shot at documenting a signup scenario, which should show up as a separate pull request)

@epilande , Just wanted to check in and see if you needed anything else done before you could merge this. Thanks.

@dandv, Interesting. Sounds like maybe I wasn't being entirely paranoid. I did end up using React Context to make sure I'm only calling useAuth once per page.

@dandv, Thanks for following up and adding a PR. That sounds great. I'll look forward to that being merged, as it will save me some code.

This is a blocker for me. I can live with the database not enforcing enums (as it has no way of knowing about them), but it would be impractical to...

For me, it had nothing to do with babel (which I wasn't using to begin with). The solution was entirely to add `"useDefineForClassFields": "false"` to my tsconfig.json. Thanks, @triesmon!

@tommybananas, Thanks for the speedy reply! Glad to know migration should be straightforward. I'm not an expert at publishing type definition files, but I think the usual approach is create...

I'm afraid I haven't had a chance yet. It is unfortunately not trivial to publish to DefinitelyTyped. Check out the [instructions](https://github.com/DefinitelyTyped/DefinitelyTyped) to see what I mean. I'm not giving up,...

Meanwhile, here is the latest file I've been working from, which in itself might help some people out until it's officially supported on DefinitelyTyped: https://gist.github.com/devuxer/77adb37a496ea756c8a735b22fed439e