Let's make context as fast as any state manager out there by only using the hooks baked right into React.
Code: github.com/jherr/fast-react-c...
👉 Practical Module Federation Book: module-federation.myshopify.c...
👉 No BS TS (The Book): no-bs-ts.myshopify.com/
👉 I'm a host on the React Round-Up podcast: devchat.tv/podcasts/react-rou...
👉 Don't forget to subscribe to this channel for more updates: bit.ly/2E7drfJ
👉 Discord server signup: / discord
👉 VS Code theme and font? Night Wolf [black] and JETBrains Mono
0:00 Introduction
0:49 Demo Application Walkthrough
4:23 Simple useState Based Context
10:24 Does Memoization Help?
11:09 Creating A Ref-Based Fast Context
24:22 Porting to useSyncExternalStore
26:04 Adding Selector Support
28:46 Making Fast Context Generic
32:38 Outroduction
#react18 #reactjs
I have been working with React for about 4 years and recently started teaching React to juniors. Today I feel like I am a junior again 😀 Thanks for sharing this amazing content Jack!!
Jack writing a solid library in real-time is just incredible. Love to see it and super empowering for anyone looking in to see that you don't need 100 npm packages in your project to make something super solid and robust! The more code that you can own and understand yourself now means more flexibility and creativity later as you figure out what your project is and can be. Also helps even if you're using pre-built libraries to explore in code yourself to know exactly what you want out of a library and cut through all the bullshit you don't need.
You have almost introduced fine-grained reactivity to React like it is for Solid and Svelte. Fantastic job 🔥 Wondering why React did not yet implement such a thing lol
Jack, thank you for all your videos! Thanks to you I leveled up my skills and got to a senior position! I hope you come out with a course soon describing all of the mid/advanced React concepts, best practices, project structuring, when and how to use 3rd party libraries like RQ, state management, and all those good stuff. I would literally pay anything for that!
'Anything'? I can imagine? kzhead.info/sun/pb57eM2sqmqAg4E/bejne.html
React Query as some excellent documentation -- dedicate a day to browse through it and you will be surprised what you will be able to accomplish with that library. My companies application has some complicated state between the server and client and react query has made it so easy to manage state, handle mutations + hydrating the client. It only took me a few days of going through the documentation and now I feel fluent with talking to that library -- it shouldn't take you very long if you dedicate a few hours to it.
@@quelchx kzhead.info/sun/fcWGYtZ9r5-jpKs/bejne.html
@@jherr I have watched this video =). When I first used RQ I thought it was more for data fetching and managing it's state but I have used it to simply manage state from one component to another and mutate that state. I love RQ it's such a useful tool. Honestly Jack I have learned a lot through your content and have taken patterns you have provided and I use them daily =).
@@quelchx Thank you so much!
Let's make react context great again :) I think the actual implementation of context should be something like this and the current version is really deficient. And again really enjoyed the way you went step by step, improved the solution, and made it generic. It not only helps with understanding the process but also demonstrates how to eat an elephant. Thanks again.
Small remark: if you are storing your data in a ref in any case, there is no need to overwrite it with a new object that destructures both the current data and the updates, instead use Object.assign to copy over the partial values for a little better performance. Otherwise, this is a nice pattern and you've done a great job showing how it comes together, @Jack Herrington!
How ? [line-22] if I use Object assign ------> store.current = Object.assign(store.current, value); but TypeScript says (Type 'Partial' is not assignable to type 'Store')
@@talatkuyuk6556 in this case, you can cast value to store. This is a shortcoming of TypeScript.
@@alexlohr7366 Nope, I casted the value as Store; but Object.assign first parameter should extend {} in nature; TypeScript is still angry.
@@talatkuyuk6556 What about this: `Object.assign(store.current, value);`
@@talatkuyuk6556 You have to constrain Store's type-note below the `Store extends Record`: export default function createFastContext(initialState: Store) { … const set = useCallback((value: Partial) => { Object.assign(store.current, value); subscribers.current.forEach((callback) => callback()); }, []);
Amazing, thank you Jack for all the value you provide with your videos
Woooah! I couldn't stress enough how much I loved this video! Thank you Jack! 🥳
Thanks for this implementation, you're a beast Jack!
Thank you Jack, the time you take to make your content..with so much thought and care makes every video a gem. Again, thank you.
This is incredibly helpful. Thank you!
Jack, this is amazing content. I never thought about the idea to use this combination between context and useRef. You are such a huge inspiration 😊
Thanks for sharing this new pattern Jack. Really helpful.
Very very cool approach. Loved it. ❤
Very sturdy implementation, just loved the approach and the way you explained. can't wait to Implement this fast context.
Jack, thanks a lot for making really excellent educational videos! This one is especially important, given how easy it is to misuse React context and end up being deep under a lot of performance issues. Thank you!
Great content as usual, it's really hard to find react content at this level so it's highly appreciated. Great pattern, love the use of refs for this
Really slick! Adopting this pattern immediately. Thanks for sharing!
Lovely video! Concise, and very helpful!! Thank you Jack :)
Exactly what I was looking for to take context to the next level. Great work as always Jack 👍
Hey man, please never stop making videos. I learn so much from you. It has been a year since I've been working full time on react apps and there hasn't been a day without something new. Thankyou.
in my eyes this should be an essential upgrade to react and should be an available hook that comes right out of the box, thanks for this!
It's incredible how much I have learned from you. Thank you once again!
This was quite amazing and answers a pretty real need I actually have right now. Thank you _so much_ for putting this out there!
came here from Codecamp, awesome content. Subbed!
That's SO VALUABLE Jack ! I was looking for a solution for exactly this problem for months. What an elegant solution !
Thank you so much for such an amazing video. This type of content is really inspiring.
This is smashing, thank you so much Jack! 🔥🔥🔥🔥
That's exactly what I was looking for! Thank you so much : )
Thank you Jack for really valuable React.js content on KZhead !
I just found out about your channel and it is impressive the way you explain. It's amazing.
What a wonderful explanation, I've been working with React for over 4 years already, and still, there's something new I get to discover every day.
Thank you so much, Jack, I have tested it, and it works great, Definitely I will use this in my production-level app.
I'm really interested in seeing how this would get involved in a more complex application, please do so Jack. For example: - involving async actions - actions that need states from different stores or fields of store
Awesome video Jack. Your videos are like goldmines.
I was looking for this exact thing for the past two days!!!! Glad I found this
I've been looking for a solution like this for years! Thanks, Jack!
I love it when these type of ideas come along. I wouldn't use it for state management, but it has a lot of potential when it comes to Multilayer contexts that I deal with at work. It piles up little by little. Thanks Jack
A superb solution, refactored to perfection. That was an excellent video, as always. Thank you Jack for all you do.
Brilliant stuff, Jack !
This tutorial is simply amazing. Thank you!
Hey long time interested, but now full fledged fan, this is hands down your best stuff to date. Amazing
Your solution is awesome; you are great guy to explain this kind of structural videos, thanks again.
Woah Jack, you are a magician and even after watching you so much, I still can’t wrap my head over some of your concepts.. humbling experience this video was.. I will come to it again a little later in life..
Jack, it's like you're following my work and post videos that are surgically relevant to my challenges. You're so awesome. Thank you so much.
Stunning work
This was so instructive, I love how you teach not only these cool patterns but the reasoning behind them AND colol little details like the Partial there. Thanks Jack!
Thanks 🙏 It's the clearest tutorial on how to implement the fast context
Great explanation, I've been toying around with using this context pattern and you explained some parts that I couldn't figure out
Jack, you a a legend! Spent most of yesterday looking at state mangers to address this kind of issue... glad I took a "KZhead break."
This tutorial blew my mind (in a positive way). Amazing stuff!
Absolute meat!!! Thank you for the tutorial Jack
That was bloody amazing
Thanks for sharing another great video sir!!
What kind of solution is this!! You just made my understanding of react to another level! Thank you so much, I'll definitely come back to watch this video again and again.
I never get tired of the view, what a zen-place to work from
Great stuff.. love these kind of videos
Amazing video, thank you Jack !
Thank you for this amazing content, really insightful.
This is pretty awesome, I just implemented this on my work
It's a rainy and windy sunday, i drink a cup of tea and i'm definitly fallen in love with your code and conception. Thank you !
My first comment to you. Your videos is super useful and straightforward. I like using Redux, but Context is super for local high state around piece of tree. I wish you GL and thanks for sharing your experience .
I really love this combo. I'm going to use fast context in UI kit I develop (for fun and practice) as I see it reasonable to use React context instead of any 3rd party state management. Less dependencies better for UI kit. I made one modification, inside Provider component there are two providers now - one provides 'set', the other 'get' and 'subscribe'. And instead of useStore there are useStoreValue and useStoreDispatch now. There are cases when you have store setter that does not care about value, so component that uses setStore will never re-render as 'set' is always stable. Thanks for the video and solution it is awesome!
Your content is amazing
That pub/sub solution is great! I'm relatively new to React and hadn't considered that as a way to manage state "globally" and only re-render components that need to. Thanks for sharing this Jack
Such a great lesson! This channel is diamond for ones who wanna become really good at react! Awesome job, thank you!
Brilliant! I need this to maintain a complex form without a complete rewrite. Thank you! 🤩
This has to be one of the best react videos I have watched. +1 Subscriber
Thank you, Jack! for your amazing content. It helps me a lot.
This is so high-quality as a junior frontend dev your contents are really helping me write neat-codes,
Thank you Jack for the best content I've ever seen, you're a great and awesome guy, and You thought me a lot
Great stuff! Thank you.
At this point, I don't really know how you keep coming up with a new cooler video. Thanks, from India
Thank you Jack, I really love this content I`m going to adjust this on my toy project now awsome!
This is one of the best tutorials on KZhead 🙌💯
Thanks Jack! Nice one.
It was really good. Thanks a lot !
This is an absolutely incredible tutorial! I learned a ton from this! I understand context, useRefs, and how components rerender SO much better now! Thank you!!!
This is the most insane video you made. This should be on npm as a library. 😁
Amazing stuff!
really great stuff!!!
Amazing man, as always.
Jack, this is by far the most interesting video about state management in React that I have ever seen. Holy shit, Sir. you are a Beast.
This is brilliant, thank you!
Thank you so much!
Using React Context and patterns like what you have shown too me is more than enough for a bunch of use cases. I'm glad to see a video like this so I can point some of our developers we hire to this video to get a gist of what I call baked into React for global state management using HOC patterns. Im sure I'm not alone with feeling like this but once you learn a few state management patterns/libraries (Zustand, Jotai, React Query, Redux, React Context patterns) I enjoy using almost all of them and when it comes to making a choice on which one to use I often struggle to make a choice because they are all great IMO (for React apps) Thanks again for all the content you provide to the React Ecosystem it's great, absolutely love the content -- your a great guy for all the work you provide towards developers coming into this gig.
thanks a lot Jack, you'r a legend!
So amazing. Thanks
good work king, love you
This is soooo goood!
I haven't seen the video yet, but based on previous videos I know it's gonna be amazing. I like that you don't only show HOW to do it, but WHY you do it. Here, you dropped this, king 👑
Done, yep, as expected, never fails to amaze.
Simply one of the smartest solution. Thumbs up ✌️👌👌
Omg just realizing that context is initially designed for slow-changing-stuff really enhanced my mental model of React. Thanks so much for your videos, you are the coding buddy I don't have :)
Awesome, thanks for your videos
Love ot, more advanced content like this please!
I've made this "fast context" solution a few times. The thing is, you don't even need any Provider here. You can just use any external object with the same pub/sub api, since we're triggering re-renders manually, so this useStore hook can pick its store from wherever, not just from a context. Also, when you do useRef(new Set(...) you're re-creating this Set for every render of that custom hook. It won't care about the value but still, it's "cleaner" to do: if (!store.current) store.current = new Set(...) to make it just happen once. Otherwise awesome content Jack. I love the useSyncExternalStore abstraction to get rid of setting up local states manually. Feels safer also to have React internals take care of that part.
Good point :D I guess this also means you could use a store that syncs with localstorage, if it made sense too
The Provider and the `useStore()` hook are fine. They decouple the components from the source which is useful for developer tests and for inclusion in design system guides. However, especially as `useSyncExternalStore` is being used, there is no need for `useStoreData()` to be a hook so it can just be implemented as a vanilla `createStore` function without all the `useRef()`and `useCallback()` complexity. Also since the properties in the created { set, get, subscribe } object are stable through the lifetime of the application it makes sense to just bind it to a `store` variable within the closure created by `createFastContext()` that both `createContext` and `StoreContext.Provider value` can use to eliminate the initial `null`.
I will never do that but hey Jack now I understand what Zustand and other state managers do at a scale. Thanks!
Love your content Jack, thanks for this great explanation! I am a React dev, I work with it every day, and this kinda of hassle that we have to go through to get this level of performance is one of my biggest pet peeves with the framework. For my freelance projects I use Svelte and I get all of that for free, it's glorious. Looking forward to a video on the new upcoming SvelteKit!
In my experience, I use React context when it is limited in a very narrow part of the components tree, when the state to share is not internal and will wrap a big part of my application, I use Redux Toolkit, I found it very awesome. For server state management, react-query for sure.
Thanks for the interesting video!
this is awesome