meteor / meteor/react-packages

React 19

Open
#406 2 comments 2 reactions 0 assignees View on GitHub
discussion
Dominant language
JavaScript
Stars
575
Forks
168
Avg merge
4d 3h
Merged PRs (30d)
1

Description

React 19 will have some awesome features which I think will work nicely with Meteor or at the very least we should take advantage of as we create a new major versions for react hooks. Bellow are some of my thoughts, but I would like to hear what everyone else has to say.

My notes so far what the next major version of the package should do:
* Remove any old workarounds and focus strictly from React 19, hopefully this will get rid of any strange behavior
* New hook to wrap `useOptimistic` hook to work seamlessly with `Meteor.call` or maybe in some way replace it so that it works better in the React paradigm. The problem here being that the simulated methods update minimongo which then re-renders the component and so on.
* `use` API seems interesting and on first look it seems to me that it could help simplify a lot of the data fetching stuff.
* Preloading API might be utilize in some fashion to improve Meteor's app load time or at the very least we could experiment here to see what we can do in the Meteor context with this. Maybe in combination with SSR we could SSR the initialization of React on the server and with it send all the rest, but this is probably a bit more out there.
* React compiler, while not in scope for these packages, we should make sure that it can be used and be recommended in the Meteor Guide, right now I have some issues.

Out of scope for this package, but to be considered is this: https://remix.run/blog/merging-remix-and-react-router

Contributor guide

No contributing guide indexed for this repository

Research direction

This is a broad proposal for a React 19 major version rather than a scoped change, and it names no files or tests. Start by reviewing the package's current React integration and comparing it with the proposed useOptimistic, use, preloading, SSR, and compiler considerations. Work is complete only after the scope and implementation approach are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.