You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the plugins don't follow the babel-plugin-${name} convention, which as result cannot be included, because babel-brunch is always adding the bable-plugin- prefix to the name here: https://github.com/babel/babel-brunch/blob/master/index.js#L36
We should somehow let the consumer specify, if the name should be used as is, or not.
My idea is to use a simple ! at the end of the plugin / preset -name
for example
plugins: {
babel: {
ignore: [/web\/static\/vendor/],
presets: ['es2015', 'es2016', 'react'],
plugins: [
"transform-object-rest-spread", // this will resolve babel-plugin-transform-object-rest-spread
"babel-root-import!", { // this will resolve babel-root-import because of `!` at the end
"rootPathSuffix": "src/js"
}]
}
The text was updated successfully, but these errors were encountered:
ghost
changed the title
Allow plugins with explicit name
Allow plugins/presets with explicit name
Oct 29, 2016
Some of the plugins don't follow the
babel-plugin-${name}
convention, which as result cannot be included, because babel-brunch is always adding the bable-plugin- prefix to the name here: https://github.com/babel/babel-brunch/blob/master/index.js#L36We should somehow let the consumer specify, if the name should be used as is, or not.
My idea is to use a simple
!
at the end of the plugin / preset -namefor example
The text was updated successfully, but these errors were encountered: