Gulp 4 Tasks Must Return Their Work to Avoid Timing Bugs
Gulp 4 builds can finish before async work completes if tasks don’t return streams or promises; returning work makes dependencies explicit and prevents missing output.
Loading…
ReadMeFeed / Community knowledge
#build
Real questions. Useful conversations. Find the people who know your stack.
gulpBuilding npm libraries with Vite's library mode: entry, externals, and CSS
Learn how to use Vite's library mode to build npm packages: configure entry, externalize dependencies, handle CSS, set UMD name, and verify the output in a consumer project.
viteConfigure @babel/preset-env with browserslist and core-js 3 usage mode
Configure Babel 7 to down‑compile syntax only for browsers that need it and inject core‑js 3 polyfills only where used, with steps to verify and recover from common misconfigurations.
javascriptKeep One Codebase for Multiple Platforms with Haxe Conditional Compilation
Learn how to use Haxe’s #if directives and -D flags to keep one codebase that compiles cleanly for JS, HXCPP, and other targets. Follow a step‑by‑step guide to set up flags, write platform‑specific blocks, verify builds, and avoid common pitfalls.
haxeClojureScript Advanced Optimizations: Shrink Production Bundles with Externs
Discover how to enable ClojureScript's :advanced compiler flag and write externs to cut bundle size by up to 70% while keeping the public API intact.
clojurescriptVite Environment Variables: Designing a Safe Client‑Side Config
Learn how to safely expose only non‑secret configuration to the browser using Vite’s VITE_-prefixed environment variables, understand the trust boundary, and verify that no secrets leak into the built bundle.
GCC Link-Time Optimization: Architecture Note
An architecture note on GCC Link-Time Optimization: requirements, minimal design, trust/data boundaries, operational checks, failure modes, and conditions that would change the design.
Diagnosing Hugo Build Slowdowns: A Step‑by‑Step Performance Guide
Learn how to spot Hugo build slowdowns, verify the root causes with template metrics and profiling, apply targeted fixes, and know when to escalate for further help.
hugoVite build.chunkSizeWarningLimit: deciding between raising the limit or manual chunking
Goal When a CI pipeline reports a failed deployment, the first step is to determine whether a Vite build warning about oversized chunks is the root cause or merely a side effect. The warning appears after a production build if any emitted chunk exceeds the build.chunkSizeWarningLimit (default 500 kB of minified, uncompressed output). Because the build still
vitejs