乱立とはいいつつ、覇権である Webpack, Babel, ESLint, Prettier 使っておけば困らないみたいなところはありそう。歴史があるので複雑だったり、JSで書かれているので速くはないみたいな欠点はあり、それで代替が色々出てるけど、しかしカスタマイズとかを考えると次の覇権が決まるまでは意外に時間かかるのでは
November 12, 2025 at 2:41 AM
乱立とはいいつつ、覇権である Webpack, Babel, ESLint, Prettier 使っておけば困らないみたいなところはありそう。歴史があるので複雑だったり、JSで書かれているので速くはないみたいな欠点はあり、それで代替が色々出てるけど、しかしカスタマイズとかを考えると次の覇権が決まるまでは意外に時間かかるのでは
I’ve been replacing webpack with vite on a Silverstripe site, and this one task has taught me more about managing build environments than the entire last year of work 🫠
November 12, 2025 at 12:49 AM
I’ve been replacing webpack with vite on a Silverstripe site, and this one task has taught me more about managing build environments than the entire last year of work 🫠
Webpack and Frontend Build-Time Performance Engineering for React web apps rudolfolah.com/profiling-we...
Webpack and Frontend Build-Time Performance Engineering for React – Rudolf Olah
rudolfolah.com
November 11, 2025 at 8:21 PM
Webpack and Frontend Build-Time Performance Engineering for React web apps rudolfolah.com/profiling-we...
Remove webpack hints IDE config (mjankowski)
https://github.com/mastodon/mastodon/pull/36769
https://github.com/mastodon/mastodon/pull/36769
Remove webpack hints IDE config by mjankowski · Pull Request #36769 · mastodon/mastodon
This was added ~6 years ago to enable IDE hints for webpack - #13012 - since we're no longer using webpack, and since IntelliJ has native Vite support - https://www.jetbrains.com/help/idea/vite...
github.com
November 11, 2025 at 11:31 AM
Remove webpack hints IDE config (mjankowski)
https://github.com/mastodon/mastodon/pull/36769
https://github.com/mastodon/mastodon/pull/36769
その後、非ブラウザ系のJavaScriptは
・CLI、特にJavaScriptアプリ自体の開発ツール (Webpackとか)
・Electronとnwjs
・サーバーサイドJS
・組み込み(GASとか)
といった感じで広く使われている。
・CLI、特にJavaScriptアプリ自体の開発ツール (Webpackとか)
・Electronとnwjs
・サーバーサイドJS
・組み込み(GASとか)
といった感じで広く使われている。
November 10, 2025 at 12:54 PM
その後、非ブラウザ系のJavaScriptは
・CLI、特にJavaScriptアプリ自体の開発ツール (Webpackとか)
・Electronとnwjs
・サーバーサイドJS
・組み込み(GASとか)
といった感じで広く使われている。
・CLI、特にJavaScriptアプリ自体の開発ツール (Webpackとか)
・Electronとnwjs
・サーバーサイドJS
・組み込み(GASとか)
といった感じで広く使われている。
Ouch. I got a phone call today from my colleague working in security asking about webpack-karma. I started to explain and he said how his CPU jumped to 100% when he tried to run the tests. He checked the package and found it was update 3 years ago. This was an audit for one of our clients.
November 9, 2025 at 4:01 PM
Ouch. I got a phone call today from my colleague working in security asking about webpack-karma. I started to explain and he said how his CPU jumped to 100% when he tried to run the tests. He checked the package and found it was update 3 years ago. This was an audit for one of our clients.
Spawning is virtually free if you're using a modern bundler. I'm not talking about 2015 webpack that took 5m to build an app (although, notice *build* still). Vite spawns fast. Modern webpack is better, too. There's Turbopack, there's buildless apps as well.
November 7, 2025 at 8:47 PM
Spawning is virtually free if you're using a modern bundler. I'm not talking about 2015 webpack that took 5m to build an app (although, notice *build* still). Vite spawns fast. Modern webpack is better, too. There's Turbopack, there's buildless apps as well.
I just opened up an old webpack project with full page auto refresh...
"you mean I have to wait a full second for the thing to reload?"
"you mean I have to wait a full second for the thing to reload?"
a man wearing sunglasses is smoking a cigarette in front of a shoe display
ALT: a man wearing sunglasses is smoking a cigarette in front of a shoe display
media.tenor.com
November 7, 2025 at 7:05 PM
I just opened up an old webpack project with full page auto refresh...
"you mean I have to wait a full second for the thing to reload?"
"you mean I have to wait a full second for the thing to reload?"
#459251 openapi-python-client: 0.27.0 -> 0.27.1
#459250 jshint: migrate from nodePackages
#459249 qwen-code: 0.1.1 -> 0.1.4
#459248 sentry-native: 0.12.0 -> 0.12.1
#459241 python3Packages.django-webpack-loader: 3.2.1 -> 3.2.2
#459239 nodePackages.fx: alias to pkgs.fx
#459250 jshint: migrate from nodePackages
#459249 qwen-code: 0.1.1 -> 0.1.4
#459248 sentry-native: 0.12.0 -> 0.12.1
#459241 python3Packages.django-webpack-loader: 3.2.1 -> 3.2.2
#459239 nodePackages.fx: alias to pkgs.fx
November 7, 2025 at 12:05 AM
#459251 openapi-python-client: 0.27.0 -> 0.27.1
#459250 jshint: migrate from nodePackages
#459249 qwen-code: 0.1.1 -> 0.1.4
#459248 sentry-native: 0.12.0 -> 0.12.1
#459241 python3Packages.django-webpack-loader: 3.2.1 -> 3.2.2
#459239 nodePackages.fx: alias to pkgs.fx
#459250 jshint: migrate from nodePackages
#459249 qwen-code: 0.1.1 -> 0.1.4
#459248 sentry-native: 0.12.0 -> 0.12.1
#459241 python3Packages.django-webpack-loader: 3.2.1 -> 3.2.2
#459239 nodePackages.fx: alias to pkgs.fx
Would love to see webpackage get steam. There's such a weird array of different bundlers that app devs use, and webpackage both gives users cool capabilities for offline web stuff, and can bring together the different dev approaches. With less source maps.
github.com/WICG/webpack...
github.com/WICG/webpack...
GitHub - WICG/webpackage: Web packaging format
Web packaging format. Contribute to WICG/webpackage development by creating an account on GitHub.
github.com
November 6, 2025 at 7:37 PM
Would love to see webpackage get steam. There's such a weird array of different bundlers that app devs use, and webpackage both gives users cool capabilities for offline web stuff, and can bring together the different dev approaches. With less source maps.
github.com/WICG/webpack...
github.com/WICG/webpack...
If I bundle everything into chunks and load with non-module script tags, and transpile away most ESM… what was the point? I remember when I was told webpack was just there to transpile ES6 for IE and would soon be no longer needed. Yet here we are.
</rant>
Hope that perspective is understandable?
</rant>
Hope that perspective is understandable?
November 6, 2025 at 11:47 AM
If I bundle everything into chunks and load with non-module script tags, and transpile away most ESM… what was the point? I remember when I was told webpack was just there to transpile ES6 for IE and would soon be no longer needed. Yet here we are.
</rant>
Hope that perspective is understandable?
</rant>
Hope that perspective is understandable?
We've merged and released an initial turbopack support for next-yak 🎉🎉
All features work out of the box aside from imports in .yak.ts files.
It also tackles long standing issues and should work generally better than the webpack version.
All features work out of the box aside from imports in .yak.ts files.
It also tackles long standing issues and should work generally better than the webpack version.
November 6, 2025 at 8:02 AM
We've merged and released an initial turbopack support for next-yak 🎉🎉
All features work out of the box aside from imports in .yak.ts files.
It also tackles long standing issues and should work generally better than the webpack version.
All features work out of the box aside from imports in .yak.ts files.
It also tackles long standing issues and should work generally better than the webpack version.
Got the browser extension building with Webpack and the NPM modules moved over to their respective GitHub repositories. Project is looking good, but that transition over from workspaces to remote-hosted modules had me wading in some esoteric JS stuff, since I'm shipping TypeScript code, and not JS.
November 6, 2025 at 5:40 AM
Got the browser extension building with Webpack and the NPM modules moved over to their respective GitHub repositories. Project is looking good, but that transition over from workspaces to remote-hosted modules had me wading in some esoteric JS stuff, since I'm shipping TypeScript code, and not JS.
We tried both, measured, and shipped. Vite or Webpack Fast Refresh – what won for ilert-ui? 👉 Read the latest blog post from our Engineering team: www.ilert.com/blog/webpack... #Vite #WebpackFastRefresh
Webpack Fast Refresh vs Vite: What was Faster for ilert‑ui | ilert
A qualitative look at ilert-ui’s local dev: comparing Vite and webpack Fast Refresh to see what truly improves daily DX.
www.ilert.com
November 4, 2025 at 8:34 AM
We tried both, measured, and shipped. Vite or Webpack Fast Refresh – what won for ilert-ui? 👉 Read the latest blog post from our Engineering team: www.ilert.com/blog/webpack... #Vite #WebpackFastRefresh
Origin
muffinman.io
November 4, 2025 at 2:39 AM
Se você usa Webpack ou Vite, eles identificam que o arquivo é o mesmo e não repetem ao compilar o projeto.
Isso segue o princípio de que deve ser fácil destruir qualquer parte do seu projeto.(+)
Isso segue o princípio de que deve ser fácil destruir qualquer parte do seu projeto.(+)
November 2, 2025 at 7:46 PM
Se você usa Webpack ou Vite, eles identificam que o arquivo é o mesmo e não repetem ao compilar o projeto.
Isso segue o princípio de que deve ser fácil destruir qualquer parte do seu projeto.(+)
Isso segue o princípio de que deve ser fácil destruir qualquer parte do seu projeto.(+)
CSS puro/HTML e React + Vite/Webpack tem pequenas diferenças cabulosas 👍🏽
November 2, 2025 at 2:12 PM
CSS puro/HTML e React + Vite/Webpack tem pequenas diferenças cabulosas 👍🏽
Great article — you perfectly captured why Module Federation is a real step forward beyond iframes 👏
Check out my MFE Orchestrator — a community-driven open-source project built to visually orchestrate micro-frontends with Vite, Webpack, and Module Federation.
mfe.orchestrator.dev
Check out my MFE Orchestrator — a community-driven open-source project built to visually orchestrate micro-frontends with Vite, Webpack, and Module Federation.
mfe.orchestrator.dev
mfe.orchestrator.dev
November 2, 2025 at 9:33 AM
Great article — you perfectly captured why Module Federation is a real step forward beyond iframes 👏
Check out my MFE Orchestrator — a community-driven open-source project built to visually orchestrate micro-frontends with Vite, Webpack, and Module Federation.
mfe.orchestrator.dev
Check out my MFE Orchestrator — a community-driven open-source project built to visually orchestrate micro-frontends with Vite, Webpack, and Module Federation.
mfe.orchestrator.dev
Starting today, you can join the open beta and experience how #microfrontend orchestration should feel.
Built for #Vite, #Webpack, and many more, MFE Orchestrator gives you the power to unify your frontend ecosystem — without the pain.
👉 Try it now: mfe-orchestrator.dev
Built for #Vite, #Webpack, and many more, MFE Orchestrator gives you the power to unify your frontend ecosystem — without the pain.
👉 Try it now: mfe-orchestrator.dev
November 2, 2025 at 9:28 AM
Starting today, you can join the open beta and experience how #microfrontend orchestration should feel.
Built for #Vite, #Webpack, and many more, MFE Orchestrator gives you the power to unify your frontend ecosystem — without the pain.
👉 Try it now: mfe-orchestrator.dev
Built for #Vite, #Webpack, and many more, MFE Orchestrator gives you the power to unify your frontend ecosystem — without the pain.
👉 Try it now: mfe-orchestrator.dev
grok can you use webpack with C code
November 1, 2025 at 5:37 PM
grok can you use webpack with C code
WordPress Developer (WordPress, PHP, OOP, Composer, PHPUnit, coding standards, CSS3, MySQL, HTML, JavaScript, jQuery, VueJS, React, NPM, Gulp, Webpack, Jest, JSON, RESTful APIs, Git, SVN) #WPJobs #WPCareers jobs.wordpress.net/j...
October 31, 2025 at 8:27 PM
WordPress Developer (WordPress, PHP, OOP, Composer, PHPUnit, coding standards, CSS3, MySQL, HTML, JavaScript, jQuery, VueJS, React, NPM, Gulp, Webpack, Jest, JSON, RESTful APIs, Git, SVN) #WPJobs #WPCareers jobs.wordpress.net/j...
Sentry was on webpack too (now rspack). knip has good support for it. @webpro.nl is also very helpful if you run into blockers
October 30, 2025 at 8:41 PM
Sentry was on webpack too (now rspack). knip has good support for it. @webpro.nl is also very helpful if you run into blockers