ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #babel
When Babel 7 preset‑env is configured with useBuiltIns: 'usage', the transformation relies on core‑js to inject polyfills for newly added built‑ins. If the core‑js package is absent or its major version does not match the preset‑env expectation (e.g., v2 vs v3), the generated code may lack polyfills for APIs such as Promise or Array.prototype.flat, causing r
Goal: Determine whether @babel/preset-env with modules set to "auto" preserves ES import/export syntax or converts it to CommonJS in a given build pipeline. Constraint: Babel 7.x defaults modules to "auto", which defers the module transform decision to the calling tool. The Babel CLI may resolve auto to CommonJS, while Rollup or webpack configured for ES mod
Goal: Determine whether a .babelrc file in one workspace package can be applied to source files in another package when babelrcRoots is not explicitly configured. Constraint: Babel 7.x with @babel/core restricts .babelrc visibility to the package root by default, but rootMode and babelrcRoots can extend that boundary. It is unresolved whether the default bou
The goal is to clarify whether @babel/preset-env influences the parsing stage of Babel’s pipeline or only the transformation stage when deciding which syntax features to support for a given target list. Because the parser runs before any plugin visitors, it is unclear if preset-env loads syntax‑plugin equivalents (e.g., @babel/plugin-syntax-top-level-await)
Babel's preset‑env resolves the set of supported runtime environments by merging targets from a browserslist configuration and an explicit targets option. When both are present, the precedence governing which source takes effect is not specified in the documentation, creating ambiguity for build pipelines that depend on consistent polyfill injection. The res
Babel Preset Configuration The scope of syntax transformation within a Babel preset is determined by the specified targets configuration option. Understanding the precise boundary of transformation when using a preset is critical for predictable output. Target Definition Uncertainty What is the documented behavior for a preset when targets is omitted entirel
Babel preset-env loose mode global variable leakage When using @babel/preset-env with the loose option enabled, class constructors and methods can generate code that inadvertently references or pollutes the global scope. This occurs particularly when transforming classes that use static methods or inheritance patterns. The loose optimization bypasses certain