# Webpack Published articles for Webpack. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## JavaScript bundling and HTTP performance trade-offs DevFeed: [JavaScript bundling and HTTP performance trade-offs]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-11-23T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [JavaScript](), [HTTP](), [Caching](), [browserify](), [Webpack]() Tags: [browserify](), [cache](), [engineering](), [http](), [infrastructure](), [js](), [news](), [webpack]() ### AI overview The article examines trade-offs between bundling JavaScript files, serving them separately, and using semantically related bundles. It explains how these approaches balance HTTP request overhead, browser fetch limits, cacheability, and unused downloaded code. ### Source excerpt By Craig Silverstein Bundling JavaScript files The traditional advice for web developers is to bundle the JavaScript files ... Read more ## Optimizing Our Build Times by Migrating from Webpack to Rspack DevFeed: [Optimizing Our Build Times by Migrating from Webpack to Rspack]() Original publisher: [Read original article]() Author: Benson Pan, Software Engineer Published: 2026-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Yelp]() Topics: [Webpack](), [build times](), [monorepo](), [build performance](), [Developer experience]() Tags: [build](), [build-times](), [build-tools](), [developer-experience](), [migration-guide](), [monorepo](), [performance](), [speed](), [tooling](), [tools](), [webpack]() ### AI overview A Yelp engineering blog post explains how the team migrated monorepo builds from Webpack to Rspack. It reports an approximately 50% reduction in build time and discusses compatibility, configuration, custom plugins, and a staged rollout. ### Source excerpt Over the years, Webpack has remained the bundler of choice for many JS projects, including here at Yelp. While it has served us well, its speed has increasingly become a bottleneck as our monorepo continues to grow. Fortunately, a bunch of new build tools (Vite, Parcel, Rspack, etc.) have emerged in recent years. Each of these tools promises different ways of improving performance and developer experience. In this blog post, we'll walk through how we migrated our monorepo builds from Webpack to Rspack and achieved an approximately 50% reduction in build time. Why Rspack Our team has been closely observing... ## Upgrade Cypress To TypeScript v6 DevFeed: [Upgrade Cypress To TypeScript v6]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-04-23T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [TypeScript](), [upgrade](), [Webpack]() Tags: [cypress](), [import](), [module](), [products](), [typescript](), [upgrade](), [webpack]() ### AI overview This tutorial explains how to upgrade Cypress projects to TypeScript v6. It recommends using bundler module resolution with Webpack and adjusting transpilation and path-alias options when needed. ### Source excerpt Finally, it has happened. Cypress v15.14 supports TypeScript v6. This is a big deal ## Next.js 16 (beta) DevFeed: [Next.js 16 (beta)]() Original publisher: [Read original article]() Author: Tobias Koppers Published: 2025-10-09T20:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Caching](), [Compiler](), [Routing (disambiguation)](), [React](), [Tailwind CSS](), [TypeScript](), [ESLint](), [Webpack](), [FIRST]() Tags: [caching](), [compiler](), [eslint](), [next-js](), [performance](), [react](), [routing](), [tailwind-css](), [typescript](), [vercel](), [webpack]() ### AI overview Next.js 16 beta introduces stable Turbopack as the default bundler, filesystem caching for faster development, React Compiler support, enhanced routing, improved caching APIs, and React 19.2 features. It also includes Build Adapters API changes and breaking changes. ### Source excerpt Next.js 16 beta includes stable Turbopack, file system caching, React Compiler support, smarter routing, new caching APIs, and React 19.2 features. ## Why Does RSC Integrate with a Bundler? DevFeed: [Why Does RSC Integrate with a Bundler?]() Original publisher: [Read original article]() Published: 2025-05-30T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [React](), [Webpack](), [Vite](), [Programming]() Tags: [integration](), [modules](), [programming](), [react](), [vite](), [webpack]() ### AI overview The article explains why React Server Components (RSC) integrate with JavaScript bundlers. Because RSC sends references to executable module code as well as serialized data, bundlers help avoid inefficient network waterfalls by discovering imports and producing bundle chunks. Bundler-less ESM is possible but described as inefficient without further optimization, while realistic integrations are bundler-specific. ### Source excerpt One does not simply serialize a module. ## Next.js 15.3 DevFeed: [Next.js 15.3]() Original publisher: [Read original article]() Author: Will Binns-Smith Published: 2025-04-09T20:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [build performance](), [Instrumentation](), [Routing (disambiguation)](), [Caching](), [Webpack](), [Vercel]() Tags: [build-performance](), [build-times](), [caching](), [experimental](), [instrumentation](), [next-js](), [routing](), [typescript](), [vercel](), [webpack]() ### AI overview Next.js 15.3 introduces alpha support for Turbopack production builds, alongside client instrumentation and navigation hooks. The release also includes experimental Rspack community support and TypeScript plugin improvements. Turbopack is reported to outperform Webpack as CPU cores increase, while persistent caching remains experimental. ### Source excerpt Next.js 15.3 includes Turbopack for builds, new client instrumentation and navigation hooks, and more. ## Docusaurus 3.2 DevFeed: [Docusaurus 3.2]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-03-29T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [builds](), [build performance](), [build times](), [Caching](), [MDX](), [Server](), [Markdown](), [Webpack]() Tags: [benchmark](), [build](), [caching](), [markdown](), [mdx](), [performance](), [release](), [webpack]() ### AI overview Docusaurus 3.2 is released with faster production builds, improved development-server performance for Markdown and MDX editing, and MDX partial headings in tables of contents. Reported benchmark results show cold builds improving from 95 seconds to 66 seconds and incremental builds from 55 seconds to 22 seconds on the React Native website, with results varying by site configuration. ### Source excerpt We are happy to announce Docusaurus 3.2. ## Announcing Vue 3.4 DevFeed: [Announcing Vue 3.4]() Original publisher: [Read original article]() Published: 2023-12-28T00:00:00Z Content type: release Language: en Sources: [The Vue Point]() Topics: [Vue.js](), [Parser](), [build performance](), [API](), [changelog]() Tags: [build-performance](), [changelog](), [ecosystem](), [features](), [nuxt](), [release](), [update](), [vite](), [vue](), [webpack]() ### AI overview Vue 3.4, named "Slam Dunk," introduces a rewritten template parser that is twice as fast, a more accurate and efficient reactivity system, and several API improvements including stabilized defineModel and same-name prop-binding shorthand. The release also improves Vue SFC compilation performance and benefits related tooling and community plugins. ### Source excerpt Today we're excited to announce the release of Vue 3.4 "🏀 Slam Dunk"! This release includes some substantial internal improvements - most notably a rewritten template parser that is 2x faster, and a refactored reactivity system that makes effect triggering more accurate and efficient. It also packs a number of quality-of-life API improvements, including the stabilization of defineModel and a new same-name shorthand when binding props. This post provides an overview of the highlighted features in 3.4. For the full list of changes, please consult the full changelog on GitHub. ## Modern VS Code extension development tutorial: Building a secure extension DevFeed: [Modern VS Code extension development tutorial: Building a secure extension]() Original publisher: [Read original article]() Author: Mdu Sibisi Published: 2023-10-02T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [VS Code Extension](), [Visual Studio Code](), [Development](), [TypeScript](), [Webpack](), [Node.js](), [Command-line interface](), [Git]() Tags: [api](), [awareness](), [blog](), [building](), [cli](), [code](), [developer](), [development](), [draftdotdev](), [engineering](), [extension](), [git](), [javascript](), [node](), [tutorial](), [typescript](), [vs-code](), [webpack]() ### AI overview This tutorial explains how to build a multifunctional VS Code extension. It introduces the required tools, project scaffolding with Yeoman and the VS Code Extension Generator, and recommended TypeScript and Webpack tooling. ### Source excerpt In our first modern VS Code extension development blog post, we covered the basics of VS Code development, including the architecture and the various types you can create. This article will help you apply that knowledge by showing you how to create and code your very own VS Code extension. ## Evergreen Tooling -- More than Just CodeMods DevFeed: [Evergreen Tooling -- More than Just CodeMods]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2023-07-26T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Tooling](), [Code](), [JavaScript](), [Webpack](), [React](), [Open Source](), [Web Development]() Tags: [code](), [compatibility](), [ecosystem](), [javascript](), [maintenance](), [migrations](), [nx](), [open-source](), [plugins](), [react](), [tooling](), [updates](), [upgrades](), [webpack]() ### AI overview The article explains Nx's evergreen tooling approach, which automates migrations and updates JavaScript projects through plugins. It presents this approach as a way to keep tooling current, preserve compatibility, and reduce maintenance work. ### Source excerpt Nx's evergreen tooling approach automates migrations, updates code like a database, and uses plugins for seamless JavaScript ecosystem upgrades with backward compatibility and reduced maintenance. ## Rspack -- Getting up to speed with Nx DevFeed: [Rspack -- Getting up to speed with Nx]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2023-03-10T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Webpack](), [React](), [Rust](), [monorepo](), [JavaScript](), [TypeScript](), [Testing](), [Cypress]() Tags: [cypress](), [javascript](), [jest](), [monorepo](), [nx](), [performance](), [react](), [rust](), [tooling](), [typescript](), [webpack]() ### AI overview Nx integrates Rspack, a Rust-based rewrite and alternative to Webpack, to provide a streamlined setup for React applications. The article describes Rspack's performance-focused architecture and reports that ByteDance saw 5- to 10-fold compilation improvements in some internal applications. Nx's plugin also supports TypeScript, ESLint, Jest, optional Vite, Cypress, caching, generators, migrations, and editor extensions. ### Source excerpt Explore Nx's integration with Rspack, the Rust-based Webpack alternative that offers 5-10x faster compilation for React apps in your monorepo. ## Trim your JavaScript bundles with Firestore Lite DevFeed: [Trim your JavaScript bundles with Firestore Lite]() Original publisher: [Read original article]() Author: Christina Holland Published: 2023-03-09T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firestore](), [JavaScript](), [Webpack](), [npm](), [Web]() Tags: [firebase](), [firestore](), [how-to](), [javascript](), [npm](), [sdks](), [web](), [webpack]() ### AI overview This tutorial explains how to reduce JavaScript bundle size by using Firestore Lite for initial, one-time data loads and loading the full Firestore SDK later when real-time updates are needed. Its demo apps report bundle-size reductions of over 70% and initial load-time reductions by half. ### Source excerpt A lightweight, standalone REST-only Firestore SDK at a fraction of the regular Web SDK size. ## Next.js 13.2 DevFeed: [Next.js 13.2]() Original publisher: [Read original article]() Author: Tim Neutkens Published: 2023-02-23T18:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Search engine optimization (SEO)](), [App](), [MDX](), [API](), [React](), [TypeScript](), [Rust](), [Webpack](), [Cache]() Tags: [api](), [cache](), [mdx](), [next](), [next-js](), [react](), [rust](), [seo](), [typescript](), [webpack]() ### AI overview Next.js 13.2 introduces major improvements to the App Router, including a Metadata API for static and dynamic SEO metadata, custom Route Handlers, MDX support for Server Components, type-safe links, Turbopack improvements, and caching changes. ### Source excerpt Next.js 13.2 introduces major improvements to the App Router in preparation for stability, including SEO support, Route Handlers, MDX for Server Components, Type-Safe Links, and more. ## Setup React and Tailwind -- The Easy Way DevFeed: [Setup React and Tailwind -- The Easy Way]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2023-02-09T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [React](), [Tailwind CSS](), [configuration](), [Code](), [Web Development](), [Front end](), [migration](), [Vite](), [Webpack]() Tags: [configuration](), [frontend](), [generators](), [how-to](), [migration](), [nx](), [react](), [tailwind](), [tutorial](), [vite](), [webpack]() ### AI overview A tutorial on setting up React with Tailwind CSS using Nx code generators. It covers creating an Nx-based React project, configuring Tailwind and related CSS tooling, and migrating Create React App projects to Nx with Vite or Webpack. ### Source excerpt Learn how to quickly set up React with Tailwind CSS using Nx's code generators, including migration from Create React App and automated configuration tools. ## Testing API Calls With React Testing Library and Jest DevFeed: [Testing API Calls With React Testing Library and Jest]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2022-12-09T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [testing-library](), [Testing](), [React](), [API](), [Jest](), [Webpack]() Tags: [api](), [asynchronous](), [jest](), [react](), [testing](), [testing-library](), [webpack]() ### AI overview A tutorial showing how to test React useEffect API calls with Jest and React Testing Library, including tests for successful and failed requests. ### Source excerpt Ever since Hooks were released in React, we've been using the hook to fetch data, whether directly or abstracted away behind Redux Thunks... ## Introducing the Spin JavaScript and TypeScript SDK DevFeed: [Introducing the Spin JavaScript and TypeScript SDK]() Original publisher: [Read original article]() Author: Joel Dice Published: 2022-12-08T02:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [SDKs](), [JavaScript](), [TypeScript](), [Serverless](), [Webpack](), [React]() Tags: [javascript](), [react](), [sdk](), [serverless](), [typescript](), [webpack]() ### AI overview The Spin JavaScript and TypeScript SDK enables developers to build rich serverless applications with familiar tools including NPM, Webpack, and React. ### Source excerpt The Spin JavaScript and TypeScript SDK enables developers to build rich serverless applications using familiar tools like NPM, Webpack, React, and more. ## Next.js 13 DevFeed: [Next.js 13]() Original publisher: [Read original article]() Author: Tim Neutkens Published: 2022-10-25T16:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [React](), [Routing (disambiguation)](), [Streaming](), [Webpack](), [Rust]() Tags: [next-js](), [react](), [routing](), [rust](), [streaming](), [ui](), [webpack]() ### AI overview Next.js 13 introduces the app directory with layouts, React Server Components, streaming, improved routing, and support for component-level data fetching. It also adds Turbopack, an improved image component, and automatic self-hosted fonts, while simplifying the API. ### Source excerpt Next.js 13 introduces layouts, React Server Components, and streaming in the app directory, as well as Turbopack, an improved image component, and the brand new font component. ## Exporting Node Modules in 2022 DevFeed: [Exporting Node Modules in 2022]() Original publisher: [Read original article]() Author: David Bushong Published: 2022-09-01T20:01:47Z Content type: tutorial Language: en Sources: [Groupon Engineering -- Medium]() Topics: [CommonJS](), [npm](), [ECMAScript](), [TypeScript](), [Webpack](), [import]() Tags: [babel](), [commonjs](), [compatibility](), [import](), [javascript](), [node](), [npm](), [typescript](), [webpack]() ### AI overview This tutorial explains CommonJS and native ES Module exports in Node.js, including how modules can be imported across module systems. It also compares the output of Babel, Webpack, and TypeScript with native Node.js module behavior, highlighting compatibility concerns and TypeScript's non-standard export syntax. ### Source excerpt Groupon maintains literally hundreds of NPM modules, both open source and internal. Many of these are consumed by our custom NodeJS-based middleware web layer we call "The Interaction Tier" (itself a topic for another post someday). As folks write new modules, a common question is "what's the best way to export things from our published modules to maximize compatibility?" -- and that is the topic of this post. First, some background and history: Flavors of exported modulesCommonJS in Node In the beginning, there was CommonJS: Here are 3 sample files with exports: // export1.js - exporting individual properties w/ CommonJS 'use strict';function foo() { } exports.foo = foo; exports.bar = 42;// export2.js - exporting a single object w/ CommonJS 'use strict';function baz() { } const garply = 88; module.exports = { baz }; // dynamically (conditionally!) exported! if (Math.random() > 0.5) module.exports.garply = garply;// export3.js - exporting a bare function w/ CommonJS 'use strict';function quux() { } module.exports = quux;// sometimes there are extra properties added to the bare function quux.yadda = 42; Those CommonJS exports can be imported either into other CommonJS files or into ES Module (more on that below) files: // import.js - importing CommonJS modules into a CJS file 'use strict';const { foo, bar } = require('./export1'); const { baz, garply } = require('./export2'); if (Math.random > 0.9) { // can also dynamically decide when to import const quux = require('./export3'); // can poke into properties tacked onto functions const { yadda } = require('./export3'); }// import.mjs - importing CommonJS modules into an ESM file // node is willing to turn exported objects into named exports import { foo, bar } from './export1.js'; import { baz, garply } from './export2.js'; import quux from './export3.js'; // cannot access added property "yadda" directly; hence: const { yadda } = quux; You can read more elsewhere, but the key features are: The module files are synchron ## React Labs: What We've Been Working On - June 2022 DevFeed: [React Labs: What We've Been Working On - June 2022]() Original publisher: [Read original article]() Author: Andrew Clark, Dan Abramov, Jan Kassens, Joseph Savona, Josh Story, Lauren Tan, Luna Ruan, Mengdi Chen, Rick Hanlon, Robert Zhang, Sathya Gunasekaran, Sebastian Markbage, and Xuan Huang Published: 2022-06-15T00:00:00Z Content type: article Language: en Sources: [React Blog]() Topics: [React](), [async/await](), [Vite](), [Webpack](), [Shopify](), [Streaming](), [Vercel]() Tags: [apis](), [compatibility](), [experimental](), [insights](), [react](), [shopify](), [streaming](), [vercel](), [vite](), [webpack]() ### AI overview The React team shares research updates following the React 18 release, including work on React Server Components, async/await-based data fetching, boundary annotations, cross-ecosystem bundler semantics, and APIs for coordinating external assets across React environments. ### Source excerpt React 18 was years in the making, and with it brought valuable lessons for the React team. Its release was the result of many years of research and exploring many paths. Some of those paths were successful; many more were dead-ends that led to new insights. One lesson we've learned is that it's frustrating for the community to wait for new features without having insight into these paths that we're exploring. ## React Labs: What We've Been Working On - June 2022 DevFeed: [React Labs: What We've Been Working On - June 2022]() Original publisher: [Read original article]() Published: 2022-06-15T00:00:00Z Content type: article Language: en Sources: [React]() Topics: [React](), [async/await](), [Shopify](), [Vercel](), [Vite](), [Webpack]() Tags: [async](), [await](), [compatibility](), [experimental](), [react](), [release](), [shopify](), [vercel](), [vite](), [webpack]() ### AI overview A June 2022 React Labs update describes ongoing research following the React 18 release, including experimental React Server Components. The React team discusses adopting async/await, annotating boundaries, coordinating bundler semantics across Webpack and Vite with Vercel and Shopify, and improving asset loading APIs. The projects had no firm timelines and might change or never ship in their current form. ### Source excerpt This blog site has been archived. Go to react.dev/blog to see the recent posts. React 18 was years in the making, and with it brought valuable lessons for the React team. Its release was the result of many years of research and exploring many paths. Some of those paths were successful; many more were dead-ends that led to new insights. One lesson we've learned is that it's frustrating for the community to wait for new features without having insight into these paths that we're exploring. We typically have a number of projects being worked on at any time, ranging from the more experimental to the clearly defined. Looking ahead, we'd like to start regularly sharing more about what we've been working on with the community across these projects. To set expectations, this is not a roadmap with clear timelines. Many of these projects are under active research and are difficult to put concrete ship dates on. They may possibly never even ship in their current iteration depending on what we learn. Instead, we want to share with you the problem spaces we're actively thinking about, and what we've learned so far. Server Components We announced an experimental demo of React Server Components (RSC) in December 2020. Since then we've been finishing up its dependencies in React 18, and working on changes inspired by experimental feedback. In particular, we're abandoning the idea of having forked I/O libraries (eg react-fetch), and instead adopting an async/await model for better compatibility. This doesn't technically block RSC's release because you can also use routers for data fetching. Another change is that we're also moving away from the file extension approach in favor of annotating boundaries. We're working together with Vercel and Shopify to unify bundler support for shared semantics in both Webpack and Vite. Before launch, we want to make sure that the semantics of RSCs are the same across the whole React ecosystem. This is the major blocker for reaching stable. Asset Loa ## Optimising BBC Online's Code Splitting Strategy DevFeed: [Optimising BBC Online's Code Splitting Strategy]() Original publisher: [Read original article]() Author: Matt Williams Published: 2022-05-30T15:21:09Z Content type: article Language: en Sources: [BBC]() Topics: [JavaScript](), [Code](), [Website](), [modern web development]() Tags: [code](), [code-splitting](), [frameworks](), [javascript](), [performance](), [react](), [webpack](), [website]() ### AI overview This article explains BBC Online's code-splitting strategy for a large JavaScript website. It describes how splitting code into separate files can support parallel downloads and limit page-specific code to the pages that need it, while noting that excessive fragmentation can cause problems. The article says BBC Online's Presentation Layer had outgrown its existing strategy and introduces its use of shared core bundles. ### Source excerpt Photo by Sen on Unsplash Modern JavaScript websites are the result of complex code bases, and the code base which powers BBC Online is no exception. There are many dependencies and frameworks that we rely upon in order to provide the functionality that our end-users expect, as well as code written in-house to cater to the needs of our website and its users; being able to click a button to follow a topic, search for content and play videos all require JavaScript code to be run by the browser. For a website as large and with as many seemingly disparate needs as the BBC's various pages, the amount of code required can grow exponentially. The code needed to render a news article - with images, social media embeds, videos and onward journeys - has only small elements of commonality with the code required to power complex sports data tables - with team badges, functionality to hide or show columns based on the screen width of the user's device, display a team's form, or provide live in-page updates for events that are happening live. As such, it has long been the practice of the JavaScript community to implement code splitting. Rather than providing all of our JavaScript and dependencies into a single large file to be downloaded by the user, we can split our code into separate files. This can provide advantages on two fronts; downloading multiple smaller files can be more efficient when devices can start those downloads in parallel (though going too far and downloading too many small files can cause problems itself!), and the way that we choose to split our files can mean that some only need to be downloaded on certain pages. It is this second benefit which can be most powerful; if you have a large piece of code on your site that is only needed for a single page, then forcing users to download that code on every page is wasteful, and can cause problems for users who might have limits on the amount of data they can download on their network. We have been using code splitti ## Docusaurus 2021 Recap DevFeed: [Docusaurus 2021 Recap]() Original publisher: [Read original article]() Author: sidachen2003@gmail.com (Joshua Chen) Published: 2022-01-24T00:00:00Z Content type: article Language: en Sources: [Docusaurus Blog]() Topics: [GitHub](), [Markdown](), [TypeScript](), [Webpack](), [npm](), [test-coverage](), [Search engine optimization (SEO)]() Tags: [build-performance](), [github](), [npm](), [recap](), [seo](), [test-coverage](), [typescript](), [webpack]() ### AI overview A recap of Docusaurus's 2021 development, covering feature releases, build and accessibility improvements, blog and documentation enhancements, TypeScript migration, test coverage, package-size reduction, adoption trends, and GitHub project growth. ### Source excerpt Docusaurus has made great progress in 2021! We've seen a lot of traction and just crossed 30k stars on GitHub! ## Introducing Nuxt 3 Beta DevFeed: [Introducing Nuxt 3 Beta]() Original publisher: [Read original article]() Published: 2021-10-11T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [Vite](), [Vue.js](), [Serverless](), [TypeScript](), [Workers]() Tags: [bugs](), [community](), [documentation](), [github](), [nuxt](), [open-source](), [pull-requests](), [release](), [serverless](), [typescript](), [vite](), [vue](), [webpack](), [workers]() ### AI overview Nuxt 3 is being released as open-source beta software after more than a year of development. It supports Vue 3 and Vite, introduces a new server engine for full-stack applications, and produces portable output for Node.js, serverless, Workers, Edge-side rendering, or static deployment. The article cautions that the beta is not ready for production. ### Source excerpt 468 days after the first commit, the Nuxt 3 beta has finally arrived. Discover what's inside and what to expect from it. Yes, it includes Vue 3 and Vite ⚡ ## The new Firebase JS SDK is now GA DevFeed: [The new Firebase JS SDK is now GA]() Original publisher: [Read original article]() Author: David East Published: 2021-08-25T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [SDKs](), [JavaScript](), [Webpack](), [npm]() Tags: [firebase](), [javascript](), [js-sdk](), [launch](), [npm](), [release](), [sdk](), [upgrade](), [web](), [webpack]() ### AI overview Firebase JS SDK version 9 is generally available. It introduces a module-first, functional API designed to enable tree shaking and reduce JavaScript bundle sizes, with reported reductions of up to 80% in some scenarios. The release includes breaking changes and a compatibility library to support gradual upgrades. ### Source excerpt News, tutorials, and updates from the Firebase team. [Next page]()