Filter
Exclude
Time range
-
Near
Every generation of developers thinks software is getting simpler. It's not. We're just getting better at hiding complexity behind APIs, frameworks, and packages: - We used to manually bundle JavaScript files. Then came Webpack. Today, many developers just use Vite or Next.js. - We used to build authentication from scratch. Today, we use Clerk, Auth0, or Supabase Auth. - We used to set up analytics pipelines ourselves. Today, we call "analytics.track()". - We used to manage servers. Today, we deploy to Vercel or Render. The hard part never disappears. It just moves lower in the stack
14
おれはRAG構築版のWebpackを待っている 未来で待っている 「それ、前のプロンプトで直したはずだろ?」AI(あいつ)と僕とのディスコミュニケーションを繋ぐ架け橋を 未来で待っている
23
As a frontend engineerPlease learn: •HTML/CSS & modern layout (Flexbox, Grid) •JavaScript (ES6 ) & TypeScript •Responsive & accessible design •State management (Redux, Zustand, etc.) •Performance optimization •Component architecture & design systems •Build tools & bundlers (Vite, Webpack) •Testing (Jest, React Testing Library) •API integration & data fetching Master the fundamentals. Stop chasing every new framework. #Frontend #Coding #Programming
3
16
外出時の作業用に MacBook Neo を買ってみました 今までは iPhone の Termius から mysql コマンドを叩いていたので技術革新です RubyMine で webpack -w と Ruby のサーバを動かしながらブラウザでデバッグしても全然大丈夫! Apple の強さを感じますね
182
Replying to @AdamRackis
Feels like the real win is Vite as the contract, not any one host. The more frameworks can target a boring standard build boundary, the less every deployment platform needs its own spiritual webpack.
51
Next.js 16、Turbopackがデフォルトに。Webpackが外れて、ビルドの待ち時間が案件で体感できるくらい縮む
6
20 packages. Current versions. The kind of stack thousands of teams are running right now. Next.js 14. React 18. Express. Django. Spring. axios. jsonwebtoken. OpenSSL 3.1.4. 146 known vulnerabilities found. Live from OSV NVD GHSA. SHA-384 Merkle commitment. RS256 signed. Bitcoin-anchored. Independently verifiable. The tool doesn't have an opinion. It just shows you what's there. Free trial — no account needed: #SupplyChainSecurity #SBOM #AppSec #DevSecOps #CycloneDX #NextJS #Django @nextjs @django @webpack @expressjs @SpringFramework @SocketSecurity @anchore #CycloneDX
1
26
Webpack and distribute chonky bundles like Java bois do with fatjars ?
87
• Supports child loggers for contextual logging • Transports run in separate worker threads for log processing • Works with web frameworks like Fastify, Express, and Koa • Bundles with webpack or esbuild for browser or server use
1
14
Did you explore the webpack/Turbopack solution? We don’t preserve this semantics but we do preserve execution order which is the more important thing.
1
119
While deploying to vercel, My build kept failing due to jsdom and an erro code ERR_REQUIRE_ESM, cause by isomorphic-dompurify. This was happening because Next.js bundlers (tools like Webpack/Turbopack) and Vercel's Serverless environment treat it as a Server Component dependency. When it compiles for the server, isomorphic-dompurify attempts to resolve jsdom. However, jsdom depends on native Node/C bindings and ESM-only sub-packages, causing the Vercel builder to crash with module resolution or ERR_REQUIRE_ESM error code. I simply removed dompurify for now since it was blocking, I'll figure this out later. nevertheless, I conquered!. Visit my blog site. orashus.com/blog
I decided to go with the html output from tiptap since it was native to tiptap, seemed to be the better option, and markdown will mean going a longer route for this. I used dompurify to sanitize this html and mitigate Cross-Site Scripting (XSS) attacks.
1
1
32
Jun 13
@kuizinas is it a webpack loader or does it use anything else besides transforms? If it’s a transform only it may already work as Turbopack supports webpack loaders
1
82
The gold standard is content hashing. If the file content changes by a single character, the hash changes, the filename changes, the browser fetches the new file. Modern build tools (Webpack, Vite, Parcel) do this automatically: output: { filename: '[name].[contenthash].js' } Zero manual work.
1
1
Replying to @u5_03
キャッチアップは私もできてないんです。Webpackずっと使ってたんですが最近はViteがいいらしいですね。lobster.jsはMarkdownベースでHTMLレンダリングできる自作ライブラリです!
2
1,045
Replying to @arvidkahl
oof there's going to be such a large graveyard of technology like this. i spent so many hours in the depths of webpack and babel that ~no one will ever have to do again lol
134
Vite 6.0を用いた「W杯速報フロントエンド」の爆速ビルド手法を徹底解説!従来のWebpackやRust製のTurbopackと、コンパイル速度およびメモリ消費量を比較しながら、アクセス集中時でも即座に緊急デプロイを行えるモダンなWeb開発環境の構築ノウハウを伝授します。 yomuteku.blogspot.com/2026/0…

104
CVE-2026-45670 Source Code Disclosure in Nuxt Rspack and Webpack Builder Dev Server vulmon.com/vulnerabilitydeta…

53
You almost certainly use a project supported by the OpenJS Foundation — even if you've never heard of it. Node.js. Electron. Jest. webpack. ESLint. jQuery. Lodash. These are just some of the projects that call the OpenJS Foundation home. Together, they are downloaded billions of times each month and power applications across every industry. The OpenJS Foundation provides these projects and their maintainers with a neutral home, open governance, shared infrastructure, and security support — so they can focus on the work itself rather than the overhead of running major open source projects alone. Open source software doesn't maintain itself. It depends on people who need support and sustainable conditions to keep doing it. → Learn more about our projects: bit.ly/4vMoLC5
8
11
2,128
𝗠𝗔𝗚𝗞𝗞.𝗧𝗘𝗖𝗞 retweeted
Running a full Webpack dev environment on Termux just to serve raw HTML. I’m building a tech empire on a 6-inch screen, don't talk to me about padding and margins right now. 🛠️🥶
Top of the Morning X Family ✨ Are we building today? 🤗 Remember its Progress in the Process
1
1
659