Did you know Tailwind CSS officially provides a loader for webpack, Rspack, and Turbopack? No more PostCSS. Up to 30% faster. Rsbuild now ships a new plugin that integrates the loader out of the box:

jquery to webpack

Webpack 4 to webpack 5

In the next version of umi, we will use `@taildwindcss/webpack` loader to support tailwindcss v4 for both utoopack and webpack: github.com/umijs/umi/pull/13…

正直なところVueだReactだというのも怪しい。 所詮糖衣文法だし、肥大化したエコシステムに依存するのはいかがなものかと思う。 Webpackだ、Vue-cliだと言われていた時代に、割と初期の段階からViteに移行し、スターターテンプレートをかれこれ6年ぐらいメンテナンスしているから言えるけど。 #v_tokyo25 #vuefes

- Next.js - React - Tailwind CSS - Webpack

Web devs: no bundler config needed. No expo-* aliases. No Metro hacks. Just install and import. The web build has zero runtime references to react-native webpack/Vite/Turbopack never touch the native code.

古いwebpackプロジェクトソースコードのメンテ。 npm outdated であちこちパッケージが古びて npm auditで脆弱性も指摘されてしまうと、いろいろつらい。 脆弱性対策でnpm audit fix --force しちゃうと互換性のない新しいバージョンに入れ替わってしまってシステムが死んでしまう。

🔒 New advisory: webpack-dev-server (CVE-2026-9595). A proxy with context / and ws: true intercepts the HMR WebSocket, leaking cookies to the backend. ✅ Patched in 5.2.5 github.com/webpack/webpack-d…

Next.js 16.2.7 is the current stable release, and with it Turbopack has fully replaced Webpack as the default bundler for all Next.js applications. This is not a gradual migration anymore. Vercel made Turbopack the default in Next.js 16 back in October 2025, and by June 2026 the ecosystem has moved on. Projects still pinned to custom Webpack configs are now the exception, not the rule. The practical impact is measurable. Turbopack delivers 2 to 5 times faster production builds and near-instantaneous hot reloads in development. But the real story is what this means for the broader web development stack. The Rust-based bundler is designed to become framework-agnostic, which puts pressure on every other tool in the build pipeline to keep up or get left behind. InfiniStrategy take: If you are still running Webpack in 2026, you are paying a tax on developer time and CI costs that compounds daily. The migration window closed months ago. Audit your custom loaders, switch to Turbopack-compatible plugins, and stop treating build tooling as an afterthought. The teams winning right now treat their build pipeline as a first-class product concern. Sources: nextjs.org/blog/next-16-2-tu… abhs.in/blog/nextjs-current-… dev.to/pockit_tools/turbopac…