Florian Bienefelt

Can this be merged?

If anyone is really annoyed with manually copying the package to their repo, I've forked and republished the package with this change as `epotek:accounts-ui`, feel free to use it.

@kurapikats Here's how to setup basic translation: ```jsx import React from 'react'; import { Accounts } from 'meteor/epotek:accounts-ui'; import { T9n } from 'meteor-accounts-t9n'; import { en } from 'meteor-accounts-t9n/build/en';...

There are a lot of forks, maybe one of them could become the official replacement.

Is there no way to specify where portals should be rendered? Or do they always render in the body tag?

This will be fixed if we merge https://github.com/cult-of-coders/grapher/pull/400 :)

A simple way to get around this is to define all your direct links normally, but all your inversed links in `Meteor.startup` :)

Well, `denormalize` does in fact support what it calls "recursive caching": https://github.com/Herteby/denormalize#recursive-caching Which is exactly what I'm looking for. In the end, it does not matter if grapher properly fetches...

Fair enough. I believe you should mention some of these caveats, because this behavior is not easy to understand, and you should be able to count on grapher to return...

This would be great to allow for better css code-splitting!