devtools
vue-svelte-size-analysis
Our great sponsors
devtools | vue-svelte-size-analysis | |
---|---|---|
44 | 18 | |
650 | 300 | |
0.9% | - | |
9.9 | 0.0 | |
7 days ago | over 1 year ago | |
TypeScript | JavaScript | |
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.
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...
- https://github.com/Replayio/Protocol-Examples
-
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:
-
Replay.io: announcing our new Replay for Test Suites feature! Time-travel debug Cypress (and Playwright) tests in CI
Hiya folks! In addition to all my free time spent working on Redux, answering questions, and modding this sub, my day job is working on Replay.io. Today we're thrilled to announce our new Replay for Test Suites feature, which lets you record and time-travel debug Cypress (and Playwright) E2E tests as they ran in CI!
-
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.
-
The 2023 guide to React debugging | Raygun Blog
I currently work for Replay.io, where we're building a true time-travel debugger for JS apps. If you haven't seen it, check it out - it makes debugging so much easier, and I've solved many bugs that would have been impossible otherwise
-
Ask HN: Is debugging TypeScript worse then JavaScript?
That's not a "TypeScript" problem. That's a "JS being transpiled and bundled" problem (of which TS is just one possible example of "transpiling").
JS debuggers (browsers, VS Code, etc) normally use sourcemaps to show you what the original source looked like so you can debug that.
Also, I'll put in a plug for my day job, Replay ( https://replay.io ). Our app is meant to help simplify debugging scenarios by making it easy to record, reproduce and investigate your code.
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.
Note that Replay also works best when you have sourcemaps, same as the other debugger tools.
vue-svelte-size-analysis
- What things sveltekit offer better than other javascript frameworks?
- The State of JS 2022
-
A React Developer's First Take on Solid
but that's not true. see https://krausest.github.io/js-framework-benchmark/current.html. There is also a break-even point in bundle size where svelte gets larger compared to vue. see https://github.com/yyx990803/vue-svelte-size-analysis
-
What's next on your JavaScript framework radar for 2023? (Front End)
i did not ignore it. You can read about it here. There is break-even point where svelte falls off compared to vue as the application grows.
- Anyone know what these recent massive spikes in svelte & vue usage are from?
-
The new wave of React state management
The first version of React was released on 2013, it took almost 10 years for Suspense to exist (we _just_ got it now with React 18), that's what I'm talking about. Even functional components and hooks took a lot of time from them get and implement the idea after they tried to use ES classes and made everything much harder to manage. Context also isn't perfect, I like it but the redraw performance is not amazing and doesn't scale at all to bigger applications.
> https://github.com/yyx990803/vue-svelte-size-analysis
This is an interesting comparison I haven't seen before, I wonder if it's true for a complete application using some lib for state management, routing, etc. and if this isn't just a kind of cherry picked example. Thanks for showing this though.
-
All you need to know about the state of Vue.js in 2022
probably only true for small projects
- Solid.js feels like what I always wanted React to be
-
Memoirs of a lone JavaScript developer PART 2 : Svelte. An awful implementation of an old idea.
You are citing this: https://github.com/yyx990803/vue-svelte-size-analysis
-
JavaScript Framework TodoMVC Size Comparison
There isn't only the size of the runtime but the size of the component code. Not all components are equal. Templates in each framework compile differently. Evan You, creator of Vue put together a comparison between Svelte and Vue which was pretty illuminating.
What are some alternatives?
legend-state - Legend-State is a super fast and powerful state library that enables fine-grained reactivity and easy automatic persistence
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
jotai - 👻 Primitive and flexible state management for React
realworld - SvelteKit implementation of the RealWorld app
dark - Darklang main repo, including language, backend, and infra
vue-native-core - Vue Native is a framework to build cross platform native mobile apps using JavaScript
rr - Record and Replay Framework
qwik - Instant-loading web apps, without effort
redux-eggs - Add some Eggs to your Redux store.
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
react-redux - Official React bindings for Redux