jscodeshift Using .babelrc project file incorrectly in Babel 6 Environments about jscodeshift

[kjanoudi]

This looks like it has to do with https://github.com/facebook/jscodeshift/blob/master/src/Worker.js#L41

function setup(tr, babel) {
  if (babel === 'babel') {
    require('babel-core/register')();
  }
  transform = require(tr);
}

With babel 6+, the recommended approach is to use require('babel-register')({options}).

I think desired behavior would actually be to do this and use the .babelrc file from the project to transform the file correctly? In which case, we would just need to use the babel-register module on environments with babel 6+

[fkling]

I think desired behavior would actually be to do this and use the .babelrc file from the project to transform the file correctly?

If I understand you correctly, no. You are correct that this is the part that causes the issue, however we use babel-core/register only to convert the transformer itself, so that one can use ES6 in the transformer. This has nothing to do with the files that should be codemodded.

More generally, jscodeshift shouldn't care what else you are doing with the source files. All it sees is a list of files and it converts those files.

[kjanoudi]

@fkling Oh ok, i see what you're saying. In building the project locally and running it, i cannot seem to reproduce the error generated by the globally installed module. I will close the issue until I can

[fkling]

Basically we somehow have to prevent that jscodeshift's Babel doesn't pick up any "external" babel configurations. Not sure if that's possible though.

[kjanoudi]

@fkling Sending the babelrc: false option to wherever babel is processing the files would accomplish this, however I'm not certain where that option would be set - or if it's possible to do so without using babel 6