Reducing Babel Helper Duplication with @babel/plugin-transform-runtime
How @babel/plugin-transform-runtime centralises helper functions, cuts bundle bloat and avoids global namespace pollution, with practical configuration tips.
Loading…
ReadMeFeed / Community knowledge
#build-config
Real questions. Useful conversations. Find the people who know your stack.
Keep Grunt file configs maintainable with expand, cwd, and rename
Replace hardcoded Grunt file lists with dynamic globs, cwd resolution, and rename transforms for maintainable builds.
gruntConfigure Vite build-time values with import.meta.env without leaking secrets
Ship different API URLs per environment in Vite by using VITE_ prefixed .env files, build-time replacement via import.meta.env, and safe defaults to avoid leaking secrets.
vitejsChoosing Vite Library Mode Output Formats: ESM, CJS, UMD Trade-offs and Validation
Decide whether to ship ESM, CJS, UMD, or a combination from Vite library mode, see the trade-offs in a compact table, and follow a concrete build-and-validation workflow.
Using CMake Generator Expressions to Set Debug/Release Compile Definitions
Learn how to use CMake generator expressions to add MYAPP_DEBUG for Debug and MYAPP_OPTIMIZED for Release builds on a single target, with verification steps and recovery tips.
CMake Generator Expressions: Platform‑Specific Flags Made Simple
Learn how CMake generator expressions let you conditionally add compile flags, libraries, and definitions per configuration or platform—clean, portable, and fast. A concrete example and trade‑offs included.
cmakeNetlify Node version pinning: netlify.toml NODE_VERSION vs .nvmrc – which source wins?
Goal: ensure the Node.js version used in Netlify production builds matches the version used locally to avoid build failures that work locally but fail in production. Uncertainty: When both a NODE_VERSION variable set in netlify.toml under [build.environment] and a .nvmrc or .node-version file are present in the repository, Netlify documentation indicates the
netlifyVite chunkSizeWarningLimit: raising the warning threshold versus code-splitting the chunk
Our Vite production build prints the chunk size warning for chunks over 500 kB, and we need to decide how to handle it. As I understand it, build.chunkSizeWarningLimit only controls when the warning prints; it does not fail the build or change the output. The unresolved decision: our main chunk sits slightly above the limit. We could raise the limit to silen
vite