Babel
![babel logo](https://webcf.waybackmachine.org/web/20210225041512im_/https://raw.githubusercontent.com/github/explore/cb39e2385dfcec8a661d01bfacff6b1e33bbaa9d/topics/babel/babel.png)
Here are 6,964 public repositories matching this topic...
-
Updated
Jan 12, 2021 - JavaScript
-
Updated
Feb 22, 2021 - JavaScript
-
Updated
Feb 24, 2021 - JavaScript
-
Updated
Jan 12, 2021 - JavaScript
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Feb 24, 2021 - Rust
For the most part this just works, but functions within tagged markup get weird indent assertions, e.g.,
${collection.map((item) => {
const { prop1, prop2 } = workWith(item); // eslint: expected indentation of 4 but found 10 (indent)
return html` // eslint: expected indentation of 4 but found 10 (indent)
<${Widget} prop1=${prop1} prop2=${prop2} />
Babel Macro
-
Updated
Feb 18, 2021 - JavaScript
-
Updated
Jan 15, 2021 - JavaScript
Validate the entire tree of options passed to preset.
Maybe, each plugin can export a list of options that only babili preset understands and we can validate them only when using the preset and not when using the plugin separately.
module.exports = function plugin() {};
module.exports.options = PropTypes.object({
n: PropTypes.number
});
Or, this can be implemented in bab
-
Updated
Feb 21, 2021 - JavaScript
-
Updated
Feb 24, 2021 - JavaScript
-
Updated
Feb 24, 2021 - TypeScript
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Oct 10, 2020 - JavaScript
-
Updated
Jul 15, 2020 - JavaScript
-
Updated
Feb 12, 2021 - JavaScript
Created by Sebastian McKenzie, James Kyle, Henry Zhu, Logan Smyth, Daniel Tschinder
Released September 28, 2014
- Organization
- babel
- Website
- babeljs.io
Bug Report
Current behavior
No core-js polyfills in the final bundle.
Since babel/babel#10862 the core-js polyfill paths always have
.js
extension.In
shouldReplace
function https://github.com/babel/babel/blob/41085248560b1403b8d0f99f108491e679531c6c/packages/babel-preset-env/src/polyfills/corejs3/entry-plugin.js#L52-L64the module path is compared wi