Henry

Nice start! However I don't think replacing .babelrc.js is much of a priority for us (at least for Babel v7, it will be plenty useful in the future). You can...

I guess it didn't really make sense to do it automatically when it's a breaking change since it wouldn't run when you updated. But now I guess we could maybe?...

🙌🙌🙌🙌🙌 that's really great! thanks for taking on the suggestion! Yeah it would be great to integrate this somehow eventually. This makes repro a lot easier as well! We haven't...

cc @kellyselden on that. Right now we just manually modify package.json/config files which are all json. I just did string replacement for other files, and next I'll need to look...

aside: This issue reminds me that we should also make a website for this where you can copy paste or even drag/drop your config/package.json and it does the same thing...

Well for one thing, there isn't an easy way to handle comments other than my "idea" to parse as js and then output as js/json https://github.com/babel/babel-upgrade/pull/8#issuecomment-366723708

Actually it updated fine for me if the babelrc is at the root. I don't think you specified where the location of the babelrc was? I'm assuming you are using...

Yep I would move it into a section and explain what a macro is or link to the new post

Either ESLint/Babel works but I figured Babel if this is going to require some kind of runtime changes like instrumenting or transforming code in order to cover certain things.

@bgirard You can make a Babel transform just error with something like `throw path.buildCodeFrameError("Modules aren't supported in the REPL");` but yeah could just be a linting rule instead. I don't...