Replay.io VS Babel

Not at this time. I'm pretty full up at this point with day job ( https://replay.io ), conferences, and personal life stuff. My current ongoing Redux maintenance task is trying to revamp our "Redux Essentials" tutorial to be TS-first. Making slower progress on that than I'd wanted, but hopefully can get that wrapped up in the not _too_ distant future. Beyond that, we've got a ton of open RTK Query feature requests... - Source: Hacker News / 16 days ago

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-javascript Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API: -... - Source: Hacker News / 3 months ago

I made a Replay recording of the sandbox:. Source: 11 months ago

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! Source: 11 months ago

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... - Source: Hacker News / 12 months ago

Some of the most popular JavaScript linting tools are ESLint, JSHint, JSLint and JSCS. We're going to be using ESLint. It’s very flexible, easy to use and has the best ES6 support, which will be helpful if we introduce more modern JavaScript (that will be transpiled for older browsers using https://babeljs.io/). All rules for ESLint can be found here: https://eslint.org/docs/rules/. - Source: dev.to / 3 months ago

This simply extends the existing build process that many front-end frameworks have. After Babel's done with its transpilation, it merely executes code to compile your initial screen into static HTML and CSS. This isn't entirely dissimilar from how SSR hydrates your initial screen, but it's done at compile-time, not at request time. - Source: dev.to / 3 months ago

First, we switched the default compiler for new projects from Babel to SWC (Speedy Web Compiler). SWC is dramatically faster than Babel and requires zero configuration. We’ll continue to support Babel in any project currently using it. - Source: dev.to / 3 months ago

Nuxt.js is an open-source JavaScript framework built on Vue.js, Node.js, Vite, and Babel.js used for creating fast, cutting-edge applications. Nuxt.js possesses similar features to Next.js, with the major difference being the web framework it is compatible with. Next.js is a React framework whereas Nuxt.js is a Vue framework. - Source: dev.to / 6 months ago

Disclaimer: If you've already developed Babel or ESLint plugins, this article may not be as beneficial for you, as you're likely already familiar with the majority of the content covered here. - Source: dev.to / 8 months ago