You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
useOptimistic
hook to work seamlessly withMeteor.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.Out of scope for this package, but to be considered is this: https://remix.run/blog/merging-remix-and-react-router
The text was updated successfully, but these errors were encountered: