devtools VS pullstate

Compare devtools vs pullstate and see what are their differences.

devtools

Replay.io DevTools (by replayio)

pullstate

Simple state stores using immer and React hooks - re-use parts of your state by pulling it anywhere you like! (by lostpebble)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
devtools pullstate
44 6
648 1,064
1.9% -
9.9 0.0
7 days ago 10 months ago
TypeScript TypeScript
GNU General Public License v3.0 or later MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

devtools

Posts with mentions or reviews of devtools. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-13.
  • Is Something Bugging You?
    10 projects | news.ycombinator.com | 13 Feb 2024
    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...

    - https://github.com/Replayio/Protocol-Examples

  • Weird Debugging Tricks the Browser Doesn't Want You to Know
    4 projects | news.ycombinator.com | 10 Nov 2023
    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
    4 projects | news.ycombinator.com | 1 Aug 2023
  • Why does the `useSyncExternalStore`docs example call `getSnapshot` 6 times on store update?
    2 projects | /r/reactjs | 14 Jun 2023
    I made a Replay recording of the sandbox:
  • Firefox displayed a pop-up ad for Mozilla VPN over an unrelated page
    7 projects | news.ycombinator.com | 25 May 2023
    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?
    6 projects | /r/reactjs | 30 Apr 2023
    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
    5 projects | /r/reactjs | 25 Apr 2023
    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.
    6 projects | /r/reactjs | 25 Feb 2023
    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
    2 projects | news.ycombinator.com | 24 Feb 2023
    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
    2 projects | /r/programming | 23 Feb 2023
    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.

pullstate

Posts with mentions or reviews of pullstate. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-26.
  • ReactNative Expo File Based Routing with Firebase Authentication
    5 projects | dev.to | 26 Apr 2023
    PullState - https://lostpebble.github.io/pullstate/
  • I am sick and tired of react-redux. Who has some good alternatives?
    18 projects | /r/reactjs | 11 Sep 2022
    Pullstate. It's a lot like svelte's store.
  • The new wave of React state management
    23 projects | news.ycombinator.com | 2 Jul 2022
    And automatically, any components using uiStateStore.useState and watching the isSidebarOpen property will get updated, exactly the same as the normal useState hook - just shared.

    It's so dead simple and has made complex app-building so much easier for me.

    The one caveat is that if I have a component with many handlers, e.g. onClick, onMouseMove, onContextMenu, onMouseLeave, etc (and in some cases I do), components can get bloated. I haven't found a fix to that yet. But that's more an inherent issue with react than anything to do with state management.

    [1] https://github.com/lostpebble/pullstate

    23 projects | news.ycombinator.com | 2 Jul 2022
    I've been using Pullstate for medium-sized apps for a couple years and it's fantastic: uses Immer under the hood (so it's all immutable even if it look as it wasn't), it's API and mental model are vulgarly simple, and my impression is that it's quite performant. I also like that the store isdisentangled from the component tree, which allows for plenty of flexibility. Totally recommended!

    https://lostpebble.github.io/pullstate/

  • Tech skill shortage
    8 projects | /r/ProgrammerHumor | 14 Aug 2021
    Sounds like you're on the right track. React is very hire-able. Try out multiple store systems. The big one is react + redux. Then after you have some experience with that, try a simpler one like pullstate.

What are some alternatives?

When comparing devtools and pullstate you can also consider the following projects:

contextism - 😍 Use React Context better.

spring-boot-boilerplate - Spring Boot Boilerplate is a starter kit. This project includes : Spring Boot(v2.7.10), Spring Data JPA, Spring Validation, Spring Security + JWT Token, PostgreSQL, Mapstruct, Lombok, Swagger (Open API)

eventrix - Open-source, Predictable, Scaling JavaScript library for state managing and centralizing application global state. State manage system for react apps.

legend-state - Legend-State is a super fast and powerful state library that enables fine-grained reactivity and easy automatic persistence

jotai - 👻 Primitive and flexible state management for React

dark - Darklang main repo, including language, backend, and infra

stalin-sort - Add a stalin sort algorithm in any language you like ❣️ if you like give us a ⭐️

rr - Record and Replay Framework

Twitter Text Obj - Twitter Text Libraries. This code is used at Twitter to tokenize and parse text to meet the expectations for what can be used on the platform.

redux-eggs - Add some Eggs to your Redux store.

re-frame-10x - A debugging dashboard for re-frame. X-ray vision as tooling.