gmoneh

Was going to report this, and saw that someone beat me to it... It only works if the ProvideReactive is used first. Otherwise, the __reactiveInject__ key in the provide object...

This PR actually completely broke the ProvideReactive/InjectReactive feature. Before, it would at least work if you declared your reactive injections before the non-reactive ones. Now, any reactive injection produces the...

See PR #281 for a proposed fix. Strategy: The problem arises because both the @Provide and @ProvideReactive decorators are competing to install a provide function in the component options. So...

Yes. The ProvideReactive/InjectReactive feature is broken in 8.3.0 after this change. In my child components, I get: Injection "__reactiveInject__" not found

I’ll second this request, and would suggest to be reconsidered. There are plenty of use cases where a computed mobx and computed vue property together would be really useful.

Thanks for reconsidering this. I don't think this has to extend to all the other Vue mechanisms. There is a clear difference for example between MobX actions and Vue methods....

Having the same problem. Was going to open an issue for this but saw I’m not the only one.

You're a genius, dude. That worked. It still gives a weird name for the script (adding ?rollup_plugin blah blah blah to the path), but the important thing is that it's...