ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #babel
Stop duplicating helper functions in your JS bundles. Learn how @babel/plugin-transform-runtime reduces bundle size and prevents global namespace pollution for libraries.
Polyfill Inclusion in Unspecified Environments Babel's @babel/preset-env utilizes the useBuiltIns option to manage core-js polyfills. When set to usage , Babel analyzes the code to include only the necessary polyfills based on the defined target environment. However, uncertainty arises when no specific target environment (such as a browserslist configuration
Learn how to architect custom Babel plugins using the visitor pattern and AST paths to avoid infinite loops and tree corruption during JavaScript transformations.
What is a reliable, step‑by‑step process for taking a JavaScript project that uses Babel for transpilation and deploying it to a production environment? I need a clear workflow that covers installing Babel, configuring presets and plugins, compiling the code, and finally deploying the compiled output (e.g., to a CDN or a Node.js server). The question should
I want to upgrade Babel to take advantage of newer JavaScript features, but I need a reliable process to test the upgrade and revert to the previous version if something goes wrong. What steps should I follow to pin versions, run tests, and safely roll back?
When using babel-loader with the cacheDirectory option enabled, the loader creates a cache entry based on a hash of the source file’s content and the resolved Babel configuration. If the Babel configuration (e.g., plugin options or presets) changes while the source file’s content and modification time remain unchanged, the existing cache entry may be reused,
Babel operates on a pipeline that converts source code into an Abstract Syntax Tree (AST) via the parser and subsequently converts that AST back into code using the generator. While the AST captures the semantic structure of the JavaScript, the process of transpilation is inherently lossy regarding original source formatting. When complex AST transformations
Goal For a low‑traffic application, the primary objective is to shrink the JavaScript bundle and speed up the build by eliminating polyfills and syntax transformations that are unnecessary for the browsers actually used. Constraints & Uncertainty The targets option in @babel/preset‑env is evaluated at compile time; any change requires a full rebuild. Cho
Goal: ship the smallest polyfill set for the project’s browserslist targets without duplicating core-js modules across the bundle. The application has no global polyfill entry file, but it does have a single JavaScript entry point. With @babel/preset-env 7.x and core-js 3, useBuiltIns: "usage" scans each file and emits only polyfills for APIs actually refere
javascript
webpack