ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #babel
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-
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
corejs
javascript