Maybe the solution would be to create a ui-dev-only-flow-router-package that already includes everything needed, but only on dev.
Additionaly, i would maybe drop the router integration and just provide the ui, so that we can use it however we like (in a route, inside an admin-template, ...)
Another cool thing of course would be to have a react version of the translation ui ;-)
If you want to use the ui-dev-only package, you will still end up having blaze in your production app, even if you use react or similar.
The reason is that it needs https://github.com/nicolaslopezj/meteor-router-layer, that needs https://github.com/kadirahq/blaze-layout to be present when flowrouter is used. Blaze-layout will include blaze of course.
Maybe the solution would be to create a ui-dev-only-flow-router-package that already includes everything needed, but only on dev.
Additionaly, i would maybe drop the router integration and just provide the ui, so that we can use it however we like (in a route, inside an admin-template, ...)
Another cool thing of course would be to have a react version of the translation ui ;-)