# Webpack Webpack is a static module bundler for modern JavaScript applications that builds a dependency graph and produces bundles. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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... ## Tailwind CSS v4.3: Scrollbars, new colors, and more DevFeed: [Tailwind CSS v4.3: Scrollbars, new colors, and more]() Original publisher: [Read original article]() Published: 2026-05-08T20:00:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [modern web development](), [Webpack](), [Next.js](), [Netflix](), [Vercel]() Tags: [css](), [netflix](), [next-js](), [releases](), [tailwind](), [vercel]() ### AI overview Tailwind CSS v4.3 introduces first-party scrollbar styling, size-container utilities, direct utilities for additional CSS properties, tab-size controls, stacked and compound variants in CSS, and default values for functional utilities. The article also covers v4.2 additions, including new color palettes, a webpack plugin, logical property utilities, and OpenType feature controls. ### Source excerpt Tailwind CSS v4.3 is here with first-party scrollbar styling, even more logical property utilities, new zoom and tab-size utilities, better @variant support, and all the v4.2 stuff we shipped while forgetting blogs existed. ## 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 ## 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. ## Docusaurus 3.8 DevFeed: [Docusaurus 3.8]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2025-05-26T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [build performance](), [build times](), [Optimization](), [Cache](), [Webpack](), [Node.js](), [Netlify](), [Vercel](), [macOS]() Tags: [build-performance](), [builds](), [cache](), [macos](), [netlify](), [node-js](), [optimization](), [release](), [vercel]() ### AI overview Docusaurus 3.8 improves build performance through persistent caching, worker threads for static site generation, and other optimizations. The release also introduces Future Flags for preparing sites for Docusaurus 4 and adds new features. ### Source excerpt We are happy to announce Docusaurus 3.8. ## 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. ## Measuring and analyzing the KotlinJS bundle size - Gustavo Fão Valvassori DevFeed: [Measuring and analyzing the KotlinJS bundle size - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2024-02-16T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [kotlinjs](), [Webpack](), [JavaScript](), [Web Development]() Tags: [analyze](), [article](), [devtools](), [gradle](), [gradle-plugin](), [javascript](), [kotlin-js](), [kotlinjs](), [lighthouse](), [measuring](), [performance]() ### AI overview This tutorial explains how KotlinJS projects are compiled into JavaScript and bundled with Webpack. It presents two ways to measure and analyze bundle size: examining source maps with SourceMapExplorer or Chrome Lighthouse, and using WebpackBundleAnalyzer. ### Source excerpt Smaller JavaScript bundle size helps improve a website's loading speed and performance. In this article, we present two different ways of analyzing and measuring KotlinJS bundle size. ## Using CSS libraries with Compose for Web - Gustavo Fão Valvassori DevFeed: [Using CSS libraries with Compose for Web - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2023-12-22T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Compose](), [compose-for-web](), [CSS](), [Webpack](), [Gradle]() Tags: [cdn](), [compose](), [compose-for-web](), [compose-multiplatform](), [css](), [gotchas](), [gradle](), [kotlin-js](), [kotlin-multiplatform](), [npm](), [third-party](), [tips]() ### AI overview A tutorial on importing and using third-party CSS styles in Compose for Web. It explains three approaches: loading styles from a CDN, adding CSS files to project resources, and managing styles with NPM. It also introduces enabling CSS and SCSS support in Webpack through Gradle configuration. ### Source excerpt Using third-party styles have a few gotchas. Here are some tips and tricks to help you out. ## 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. ## 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. ## 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 ## Different ways to distribute and integrate Kotlin/JS library DevFeed: [Different ways to distribute and integrate Kotlin/JS library]() Original publisher: [Read original article]() Author: Jigar Brahmbhatt Published: 2022-07-11T20:24:11Z Content type: tutorial Language: en Sources: [Touchlab]() Topics: [Kotlin](), [Library](), [Gradle](), [JavaScript](), [Webpack](), [npm](), [TypeScript](), [browser]() Tags: [browser](), [coding](), [community](), [development](), [engineering](), [gradle](), [inclusive](), [javascript](), [kotlin](), [kotlinjs](), [kotlinmultiplatform](), [library](), [npm](), [software](), [typescript](), [webpack]() ### AI overview A tutorial on distributing and integrating Kotlin/JS libraries in a Kotlin Multiplatform setup. It explains browser and Node.js targets, library and executable binaries, Gradle distribution tasks, Webpack bundles, and publishing output as an npm module with JavaScript and TypeScript usage. ### Source excerpt Note that examples in this post use Kotlin 1.7.0 In the previous post in the Kotlin/JS series, we learned about @JsExport to expose Kotlin code on the JS side. Now, we would look at various ways to distribute a JS library code through a KMP setup. Table Of Contents Gradle Setup Webpack Node Module npm-publish Using the library Use webpack executable HTML JavaScript TypeScript Use as node module HTML JavaScript TypeScript Gradle Setup If you don't already have a JS target in your KMP library project, then you should check out this blog post first. Let's look at common options to use for JS target, js(IR) { browser() nodejs() binaries.library() binaries.executable() } browser() It sets the JavaScript target execution environment as browser. It provides a Gradle task--jsBrowserTest that runs all js tests inside the browser using karma and webpack. nodejs() It sets the JavaScript target execution environment as nodejs. It provides a Gradle task--jsNodeTest that runs all js tests inside nodejs using the built-in test framework. binaries.library() It tells the Kotlin compiler to produce Kotlin/JS code as a distributable node library. Depending on which target you've used along with this, you would get Gradle tasks to generate library distribution files. Kotlin browser tasks -------------------- jsBrowserDevelopmentLibraryDistribution jsBrowserDevelopmentLibraryPrepare jsBrowserProductionLibraryDistribution jsBrowserProductionLibraryPrepare Kotlin node tasks ----------------- jsNodeDevelopmentLibraryDistribution jsNodeDevelopmentLibraryPrepare jsNodeDevelopmentRun jsNodeProductionLibraryDistribution jsNodeProductionLibraryPrepare jsNodeProductionRun jsNodeRun EitherjsBrowserProductionLibraryDistribution or jsNodeProductionLibraryDistribution task generates output files in /build/productionLibrary folder binaries.executable() It tells the Kotlin compiler to produce Kotlin/JS code as webpack executable .js files. Enabling this option generates the following Grad ## 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 ## 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. ## Upgrading Webpack 4 -\> 5 DevFeed: [Upgrading Webpack 4 -\> 5]() Original publisher: [Read original article]() Author: Hiroki Osame Published: 2021-08-18T23:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Webpack](), [build times](), [Caching](), [migration]() Tags: [build](), [build-times](), [caching](), [engineering](), [migration-guide](), [webpack]() ### AI overview Square's Ecommerce Performance team describes upgrading its largest Ecommerce codebase from Webpack 4.46.0 to Webpack 5.3.7. Following the migration guide, they achieved about a 30% bundle-size reduction, faster development builds through persistent caching, stricter checks, and typed Webpack code. ### Source excerpt Smaller bundles, faster build times, stricter checks, and fully typed ## Deep dive into the new Firebase JS SDK design DevFeed: [Deep dive into the new Firebase JS SDK design]() Original publisher: [Read original article]() Author: David East Published: 2021-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [SDKs](), [JavaScript](), [Developer experience](), [Webpack](), [Web]() Tags: [compatibility](), [developer-experience](), [ecosystem](), [firebase](), [javascript](), [sdk](), [techniques](), [web](), [webpack]() ### AI overview This deep dive explains why Firebase redesigned its JavaScript SDK around native modules and modular organization. The change enables tree shaking, which can remove unused code and improve web application performance, while requiring a break from the longstanding API. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Introducing the new Firebase JS SDK DevFeed: [Introducing the new Firebase JS SDK]() Original publisher: [Read original article]() Author: David East Published: 2021-07-27T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [SDKs](), [JavaScript](), [Webpack](), [npm]() Tags: [firebase](), [javascript](), [js](), [js-sdk](), [npm](), [sdk](), [tutorials](), [updates](), [web](), [webpack]() ### AI overview Firebase introduces beta JavaScript libraries that are significantly smaller, with some reduced by up to 80%. The update uses explicit exports and individual package entry points to enable tree-shaking, but changes the library API and requires code updates. ### Source excerpt News, tutorials, and updates from the Firebase team. ## A Demo of a Service-Worker-Based Build Tool for Ember DevFeed: [A Demo of a Service-Worker-Based Build Tool for Ember]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2021-03-30T23:01:57Z Content type: article Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [Webpack](), [Tool]() Tags: [build-tool](), [demo](), [ember](), [talk](), [tools](), [webpack]() ### AI overview This post accompanies a talk from EmberConf 2021 and presents a demo of a service-worker-based build tool for Ember. It implements enough of the Embroider v2 specification to crawl addon metadata and combine public assets, but remains incomplete and demo-quality. ### Source excerpt This post serves as a permalink to accompany my talk from EmberConf 2021. Mho The demo of the service-worker-based build tool is available here with instructions to run both the prebuilt binary (currently compiled only for OSX, sorry!) as well as how to rebuild everything yourself. It' [Next page]()