As a react dev considering hilla, I can confidently say my evaluation would be over if a newer react router was introduced replacing react with preact. This has been announced as I understand. Setting the preact signals asside, for my use case and any future it matters. Preact is not an acceptable replacement regardless of the compatibility claims.
So, I would like to offer this request as I evaluate Vaading Hilla for existing react projects. I’d love to join the java backend again.
Hi,
Hilla uses React, not Preact.
We are pushing the usage of Preact signals, but as a React library, to be able to develop full-stack signals on top of them.
You are not required to use signals, you can still use React state hooks.
Understood that hilla uses react; However, React-Router (aka Remix) is planning their own fork of Preact in some Remix v3. Remix v3 may be its own thing, will React-Router continue? probably. But, for now React is important for any migration and preact or a fork would not be. Thanks for the reply @Luciano_Vernaschi and glad to see Vaadin is committed to React.
The signals are not an issue, just the Remix direction change.