<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Frontend on Kaisekukun</title><link>https://netguide.jp/en/tags/frontend/</link><description>Recent content in Frontend on Kaisekukun</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Kaisekukun</copyright><lastBuildDate>Sun, 10 May 2026 12:00:00 +0900</lastBuildDate><atom:link href="https://netguide.jp/en/tags/frontend/index.xml" rel="self" type="application/rss+xml"/><item><title>Advanced Tuning for Vite Build and Bundling Performance</title><link>https://netguide.jp/en/software/vite-build-performance-tips/</link><pubDate>Sun, 10 May 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/en/software/vite-build-performance-tips/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/vite-build-performance-tips-en.png" alt="Featured image of post Advanced Tuning for Vite Build and Bundling Performance" /&gt;&lt;p&gt;Keep your Vite builds extremely fast using custom bundling settings and caching layers.&lt;/p&gt;
&lt;p&gt;Vite is lightning-fast out of the box, but as codebases expand, production builds can slow down due to heavy Rollup compilation stages. This guide outlines how to optimize your builds using &lt;code&gt;manualChunks&lt;/code&gt;, esbuild minification settings, and dependency pre-bundling configurations.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-code-splitting-balancing-asset-sizes"&gt;1. Code Splitting: Balancing Asset Sizes
&lt;/h2&gt;&lt;p&gt;By default, Vite bundles your application code into unified scripts. To prevent downloading unnecessary JavaScript during the initial page load, developers must implement robust code-splitting strategies.&lt;/p&gt;</description></item><item><title>Tailwind CSS v4 Features and Migration Guide</title><link>https://netguide.jp/en/web/tailwind-css-v4-update/</link><pubDate>Wed, 01 Apr 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/en/web/tailwind-css-v4-update/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/tailwind-css-v4-update-en.png" alt="Featured image of post Tailwind CSS v4 Features and Migration Guide" /&gt;&lt;p&gt;Tailwind CSS v4.0 introduces a brand-new compilation engine written completely in Rust, accelerating build loops by up to 10x. Additionally, it transitions from a JavaScript-based configuration file (&lt;code&gt;tailwind.config.js&lt;/code&gt;) to a CSS-first approach, where customizations are defined inside your primary stylesheet using standard CSS variables.&lt;/p&gt;
&lt;p&gt;This article reviews the major changes in Tailwind CSS v4 and provides a practical migration walkthrough to help you upgrade your projects.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-key-changes-in-tailwind-css-v4"&gt;1. Key Changes in Tailwind CSS v4
&lt;/h2&gt;&lt;h3 id="1-rust-powered-oxide-engine"&gt;1) Rust-Powered &amp;ldquo;Oxide&amp;rdquo; Engine
&lt;/h3&gt;&lt;p&gt;The defining feature of v4 is its compiler. Rewritten in Rust, the Oxide engine processes stylesheet files significantly faster than the old PostCSS-based engine. This translates to near-instantaneous dev server startups and hot module replacement (HMR), keeping developers in their flow.&lt;/p&gt;</description></item></channel></rss>