- Asked By
- Asked At
- 2017-11-09 23:03:44
Found 15 possible answers.
I found this error using custom plugin, but I suppose it shouldn't be a real plugin at all
What if it is custom? Can I create file in `test` section and mention it in `options.json`?
Do you have any custom resolution logic in your Webpack config? that error is weird
hey guys, about the problem I faced yesterday: want to make the custom plugin only works for some folder, I follow what @satya164 said to have two .babelrc and it works
I have presets: ["react-native", "flow"],
I am trying to find all classes that extended Component in react-native, then add componentWillMount() if it doesn't have one
@hxb901102 uploaded a file: Untitled https://babeljs.slack.com/files/U89NB9V1R/F8ABBPS4S/-.txt
It seems like "ClassDeclaration" is not working. Has anyone saw this happen before?
and it works, thanks everyone, really save my day
so on the root, I have a .babelrc which doesn't have my custom plugin specify, then in the ./src, I have another .babelrc that looks the same except it contains the custom plugin
Hello , anyone knows how to create a babylon custom plugin?
@sven is there a way to make my plugin runs before other plugin?
Ok, I found the reason. I have two .babelrc, one in the root dir, one in the ./src dir. There reason I have two is I want to only apply the custom plugin for the ./src not the node_modules. However, the .babelrc in the root dir will be run first and transform all ClassDecalaration before the custom plugin starts parsing. If I add the custom plugin in the root .babelrc, it works fine.
Hi guys, I am writing a custom plugin and I would like it only traverse the ./src directory, is there a way to specify this in .babelrc? Thanks
does babel-cli ignore node_modules files by default? If so, how can I make it not ignore them?
that ASI PR is funny
is it standard to transpile down things in node_modules now? we had to switch away from a dependency because it switched to using arrow functions in the code on npm
given the amount of custom tooling for “standard”, maybe they should just release their own custom transpiler from standard-js to real js – and have newlines be syntactically significant there
Are you using other plugins other than the one you are creating on your local machine?
are you saying your JS code itself would be able to analyze the scopes, or just your custom engine itself?