useTransition conflicts with React 18 useTransition hook

[a7medev]

The Problem

The useTransition hook's name conflicts with React 18 useTransition hook, I think this needs to be changed to something else so that the Remix API stays stable and doesn't change very often.

[mdingena]

You could do React.useTransition() instead.

[matmilbury]

I don't think it's a matter of variable name conflict.

It's deeper than that.

It's that when you have one word that might refer to two things, the communication becomes confusing.

[akomm]

@matmilbury you are 100% right, but can't imagine mdingena meant this as a permanent solution. I guess he just communicated to short.

[mdingena]

No, I meant as a permanent solution. Laying claim to function names across libraries is silly. You can deal with this on the consumer side. If you prefer useTransition to be a "React thing" then import Remix's version of it with import { useTransition as useRemixTransition } and just move on with your life.

[adebiyial]

Yet another JavaScript framework is a very good article about naming

[ryanflorence]

It's unlikely you'll ever interact with React.useTransition directly in Remix. We've been using the word "transition" for route transitions long before React grabbed the name. It'll be easy to change later if we need to but we're not concerned about it.

See my other comment

[kag359six]

This is a bit off topic, but isn't the React.useTransition API still useful when trying to prevent the browser from freezing up when doing expensive state updates? For example, changing a filter for a data intensive chart, or updating a large form when using a library like Formik that re-renders the entire form on state change.

Unless I'm misunderstanding that specific React API, or perhaps Remix has it's own way around those scenarios.

[ryanflorence]

FYI: As we move the remix data APIs to react router, we've renamed the hook useNavigation

let navigation = useNavigation();
navigation.state
navigation.formData
// etc.

When we re-implement Remix on top of the next version of React Router, we'll support both hooks in parallel (useTransition and useNavigation) and add a warning in useTransition to switch to useNavigation.

Then in v2 we'll remove useTransition.

I like useNavigation better, too, so I'm pretty happy about this.

(I still think React's should be called useUpdate, and then animation libs could keep useTransition. But it's cool 💙🧊💙🧊💙🧊💙)

[mikeybinns]

Currently Remix doesn't export the Transition type so we have to do ReturnType<typeof useTransition>, Is this because of this name conflict or is this just an oversight?
I feel like it should be exported because the Fetcher type is exported from that package, but perhaps I'm missing something?