reactivue

🙊 Use Vue Composition API in React components

Web Development

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

1.5KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

🙊 Use Vue Composition API in React components

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2020-09-18 16:52:38 UTC to 2024-02-03 17:32:31 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	1	1	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	0	1

What Hacker News says

3 sources

samwillis·Feb 3, 2024

I think it's a shame the reactivity/signals system from Vue 3 wasn't broken out as a separate project under a different name. They had so much success with building Vite as a separate project, and the reactivity system they built for Vue 3 is so good it warrants the same attention. It can, and is, used outside of Vue, see Alpine.js, but it's adoption would be so much greater if it was packaged under its own name. There is this project that even combines it with react: https://github.com/antfu/reactivue. I wish we had slightly looser compiling between templating and reactivity systems...

In VueJS turns 10 years old

simultsop·Jun 22, 2022Submission

Peaceful OSS

3 points · Open discussion

gavinray·Sep 18, 2020

My only wish now is for the TSX experience to be rounded out. From a reactivity standpoint, Vue has a much more ergonomic/easy to use API for handling component state, effects, and computed values (in my opinion) than React. But in the last 6-8 months, I've leaned away from Single-File Components because when you want to do something like define a bunch of small components, it's a lot more difficult to do than with multiple TSX functions you can chuck in one file. So I've been using Vue with TSX, and the experience (in the last few months only, before that was pretty bad) is okay, but not as solid as you'd get with React. I'm not the only one who must feel this way, because this exists and has a lot of stars: "Reactivue: Use Vue Composition API in React components" https://github.com/antfu/reactivue Unfortunately, this is a weird stance t

Read the rest

o take in the Vue community, almost nobody uses JSX/TSX. Because of this, the development efforts towards it aren't as much a priority. Overall, I'd rate the experience as "decent" and "totally usable", but I hope to see the DX for Vue's TSX community improve over the coming months. --- Edit 2: Disregard the below, this already exists apparently Edit 1: Having to write two type definitions for Component Props: one TS interface/type, and one as the JS object sucks. That's my one big complaint. I know it's impossible because props need a runtime value but someone should make a plugin/babel transform to decorate the "props" key from the generic argument here: const MyComponent = defineComponent<MyComponentProps> Use reflection on "MyComponentProps" to set "props" key. There's another comment below discussing this drawback too.

In Vue.js 3