jotai
devtools
Our great sponsors
jotai | devtools | |
---|---|---|
105 | 44 | |
16,982 | 648 | |
3.5% | 1.9% | |
9.2 | 9.9 | |
8 days ago | about 19 hours ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jotai
-
React State Management in 2024
Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.
-
React Basics: Essential Knowledge for Every React Developer
jotai Is the signal based state manager I recommended, offering the best developer experience (in my opinion) as it eliminates the necessity to define and update a global store
-
🚀 Dominate React Project Startups: Insider Tips for Dev Success! 🤓
Jotai 🧙♂️
-
Thoughts on Signals?
Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.
-
New Project: What is a good framework for a website?
Global State Machine: Jotai (great for any state that needs to be stored globally for your application)
-
Building an Account switcher with NextJS and Next Auth
The accounts manager is responsible for storing and managing all the accounts that users have used on your app. You can use any state management solution such as Redux, Zustand, Jotai, React Context etc.
-
Changelog #0023 — 🛠️ Internal refactoring and improvements
Most impactful has been reworking our data model layer and state management system. The original codebase had evolved to keep much of its business logic inside jotai atoms, and we generally had very little abstraction in the model layer. This made the model layer code complex, rigid, and bug-prone.
-
Which state management library should I use?
For atoms, Jotai or Zedux
-
Going from Flutter to React
You should try https://jotai.org/, its like riverpod
-
Why You Don't Need Signals in React
To simplify the process of defining and using global state, third-party libraries like Jotai can be useful. With Jotai, you can easily share state between components without relying on prop drilling or context propagation.
devtools
-
Is Something Bugging You?
Exactly - that's what we've already built for web development at https://replay.io :)
I did a "Learn with Jason" show discussion that covered the concepts of Replay, how to use it, and how it works:
- https://www.learnwithjason.dev/travel-through-time-to-debug-...
Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API:
- https://static.replay.io/protocol/
Our entire debugging frontend is built on that API. We've also started to build new advanced features that leverage that API in unique ways, like our React and Redux DevTools integration and "Jump to Code" feature:
- https://blog.replay.io/how-we-rebuilt-react-devtools-with-re...
- https://blog.isquaredsoftware.com/2023/10/presentations-reac...
-
Weird Debugging Tricks the Browser Doesn't Want You to Know
Replay's founders originally worked as engineers on the Firefox DevTools (and in fact our debugger client UI started as a fork of the FF Devtools codebase, although at this point we've rewritten basically every single feature over the last year and a half). So, the original Replay implementation started as a feature built into Firefox, and thus the current Replay recording browser you'd download has been our fork of Firefox with all the recording capabilities built in.
But, Chromium is the dominant browser today. It's what consumers use, it's devs use for daily development, and it's what testing tools like Cypress and Playwright default to running your tests in. So, we're in the process of getting our Chromium fork up to parity with Firefox.
Currently, our Chromium for Linux fork is fully stable in terms of actual recording capability, and we use it extensively for recording E2E tests for ourselves and for customers. (in fact, if you want to, all the E2E recordings for our own PRs are public - you could pop open any of the recordings from this PR I merged yesterday [0] and debug how the tests ran in CI.)
But, our Chromium fork does not yet have the UI in place to let a user manually log in and hit "Record" themselves, the way the Firefox fork does. It actually automatically records each tab you open, saves the recordings locally, and then you use our CLI tool to upload them to your account. We're actually working on this "Record" button _right now_ and hope to have that available in the next few weeks.
Meanwhile, our Chrome for Mac and Windows forks are in early alpha, and the runtime team is focusing on stability and performance.
Our goal is to get the manual recording capabilities in place ASAP so we can switch over and make Chromium the default browser you'd download to make recordings as an individual developer. It's already the default for configuring E2E test setups to record replays, since the interactive UI piece isn't necessary there.
Also, many of the new time-travel-powered features that we're building rely on capabilities exposed by our Chromium fork, which the Firefox fork doesn't have. That includes the improved React DevTools support I've built over the last year, which relies on our time-travel backend API to extract React component tree data, and then does post-processing to enable nifty things like sourcemapping original component names even if you recorded a production app. I did a talk just a couple weeks ago at React Advanced about how I built that feature [1]. Meanwhile, my teammate Brian Vaughn, who was formerly on the React core team and built most of the current React DevTools browser extension UI, has just rebuilt our React DevTools UI components and started to integrate time-travel capabilities. He just got a working example of highlighting which props/hooks/state changed for a selected component, and we've got some other neat features like jumping between each time a component rendered coming soon. All that relies on data extracted from Chromium-based recordings.
[0] https://github.com/replayio/devtools/pull/9885#issuecomment-...
[1] https://blog.isquaredsoftware.com/2023/10/presentations-reac...
- Evading JavaScript Anti-Debugging Techniques
-
Why does the `useSyncExternalStore`docs example call `getSnapshot` 6 times on store update?
I made a Replay recording of the sandbox:
-
Firefox displayed a pop-up ad for Mozilla VPN over an unrelated page
FWIW, the Firefox devs who were doing the WebReplay time travel debugging POC weren't, as far as I know, fired. Instead, they left and started Replay ( https://replay.io ), a true time-traveling debugger for JavaScript.
I joined Replay as a senior front-end dev a year ago. It's real, it works, we're building it, and it's genuinely life-changing as a developer :)
Not sure how well this would have fit into Firefox as a specific feature, given both the browser C++ runtime customizations and cloud wizardry needed to make this work. But kinda like Rust, it's a thing that spun out of Mozilla and has taken on a life of its own.
Obligatory sales pitch while I'm writing this:
The basic idea of Replay: Use our special browser to make a recording of your app, load the recording in our debugger, and you can pause at any point in the recording. In fact, you can add print statements to any line of code, and it will show you what it would have printed _every time that line of code ran_!
From there, you can jump to any of those print statement hits, and do typical step debugging and inspection of variables. So, it's the best of both worlds - you can use print statements and step debugging, together, at any point in time in the recording.
See https://replay.io/record-bugs for the getting started steps to use Replay, or drop by our Discord at https://replay.io/discord and ask questions.
-
What is not taught in React courses, but is commonly used in a real job and overlooked?
I also recently did a Learn with Jason show episode based on this, where we went through many of the same topics, and also looked at the Replay.io time-traveling debugger that I build as my day job:
-
Dan Abramov responds to React critics
My day job is working at a company called Replay ( https://replay.io ), and we're building a true "time traveling debugger" for JS. Our app is meant to help simplify debugging scenarios by making it easy to record, reproduce and investigate your code.
-
Introducing Suspense: APIs to simplify data loading and caching, for use with React Suspense.
Not directly, no. Brian used to be part of the React core team, but he (and I) both joined https://replay.io last year. We've built up these utils as we've been refactoring our codebase, and Brian extracted them into their own package.
-
Omniscient Debugging
Yep, my day job is working on the Replay time-traveling debugger for JS ( https://replay.io/ ).
Also saw someone post an indie gaming company's TTD development environment yesterday:
https://www.reddit.com/r/programming/comments/11a2meo/tomorr...
-
Tomorrow Corporation's time travelling debugger, including debugging other people's play sessions, hot asset reloading, live compilation on every keystroke and more
I actually work for Replay ( https://replay.io ), where we're building a time-traveling debugger for JS apps. It's interesting to hear some of the similarities and differences in approaches and usages, since this is the kind of thing I work with on a daily basis myself.
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
signals - Manage state with style in every framework
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
redux-thunk - Thunk middleware for Redux
hookstate - The simple but very powerful and incredibly fast state management for React that is based on hooks
effector-react - Business logic with ease ☄️
nanostores - A tiny (286 bytes) state manager for React/RN/Preact/Vue/Svelte with many atomic tree-shakable stores
use-cookie-state - State management React hook using browser cookies as persistent storage