ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #babel
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 measure how each Babel plugin or preset contributes to overall build time in order to identify optimization opportunities. The process must allow me to establish a reliable baseline, isolate the effect of single items, and account for monorepo configurations where Babel may need to locate the root configuration. What approach yields a consistent ba
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
Context For a low‑traffic web app, every kilobyte of JavaScript counts. Core‑JS 3 offers selective imports (e.g., import 'core-js/modules/es.array.flat'; ) and a runtime detector ( import 'core-js/actual'; ) that can trim polyfills. Babel’s useBuiltIns: "usage" automatically injects only the polyfills that the target browsers actually need. However, Core‑JS
When processing modern JavaScript syntax in Babel 7.x, the @babel/parser component throws an "Unexpected token" error if it encounters optional chaining syntax without the appropriate plugin enabled. While enabling @babel/plugin-proposal-optional-chaining resolves the parsing failure, a configuration uncertainty arises when this is paired with @babel/plugin-
Goal: Determine whether the datetime2 package should provide a generic mechanism to update the time zone offset when the document language is changed via babel, so that displayed times reflect the correct regional offset including daylight‑saving adjustments. Currently, datetime2 loads a static offset at package initialization and only offers \\DTMsetoffset
javascript
webpack
corejs
latex