I can add tests for Solid if you'd like :)

That said, I know that the setCurrentInstance was a blocker previously. I generally agree we should wait until that PR merges and releases before this moves forward

I can add tests for Solid if you'd like :)

That said, I know that the setCurrentInstance was a blocker previously. I generally agree we should wait until that PR merges and releases before this moves forward

Yeah, feel free to take it.

I was thinking the same about setCurrentInstance. But postinstall hook just worked really well and I changed my mind. @antfu using same approach for vue-demi. I don't think we have to wait for official support before releasing this.

Generally LGTM, I think you could take the lead and merge it when you think it's ready.

To be careful, we could do a few beta release before the stable one. And also it would be great to have a migration guide in readme.

Now, defineComponent support omitting render function. So, you can return your React component within a computed and use your refs directly without duplicating returned expression on render function. This is React only feature.

export const App = defineComponent(() => {
  const counter = ref(0)

  return computed(() => (
    <div>
      <p>Count: {counter.value}</p>
      <button onClick={() => (counter.value += 1)}>Increment</button>
    </div>
  ))
})

I like the new interface, and well done! I am fine with postinstall approach (probably hard to make Vue expose them), but I think adding a section about How it works with the mention of we how and why we are using postinstall would be better.

Otherwise, feel free to merge when you think it's ready. You can ping me when there is any action needs on my side. Thank you!

Is there some body can merge this PR ?

Is there any work left to do on this? Would love to help out if needed.
@sibbng

• I'm not happy about the way we patch vue. It does require side-effects-cache=false and shamefully-hoist=true in .npmrc file for pnpm. It would be nice to have a standalone build that works like 0.x version.

• Thinking of removing Solid implementation as it is not on par with React and an extra mental overhead.

• The way Babel plugin work is too cryptic. It transforms anonymous functions to defineComponent calls.

export const App = () => {
  const counter = ref(0)

  return (
    <div>
      <p>Count: {counter.value}</p>
      <button onClick={() => (counter.value += 1)}>Increment</button>
    </div>
  )
}

Will be compiled to:

export const App = defineComponent(() => {
  const counter = ref(0)

  return computed(() => (
    <div>
      <p>Count: {counter.value}</p>
      <button onClick={() => (counter.value += 1)}>Increment</button>
    </div>
  ))
})

Babel plugin shouldn't be part of this package.

• PROPS_UPDATED hook makes component rerendering significantly slower. Maybe reactivue components should be pure and shouldn't depend on props. I'm open for alternative suggestions.
• We should make it clear that Reactivue is not built to be used in production apps.

I will not be able to work on all these stuff for the foreseeable future. For the time being I'm not interested in working on experimental stuff.

If you want to push it forward feel free to make a PR for the next branch. I will do my to review it.

Would be possible to omit the return computed() and allow to just return the render function return () => , which can then be wrapped on a computed automatically?

I believe that a valuable action right now would be a small-scale refactoring to make the 0.x version compatible with Vue 3.2