Closed jedwards1211 closed 8 years ago
Do the maintainers have a .babelrc
lurking in a parent directory?
this may be because jscodeshift uses babel5 which has an outdated parser. this is mentioned in the README, but doesn't say what things are known to not parse... not sure if this is one of them. @bhosmer?
oh, maybe i misread. this isn't even able to parse the transform? i thought you were saying it hit one of your files that it couldn't transform, not that the transform itself doesn't load.
Right, I saw that note in the README but it's the codemod script itself that jscodeshift fails to parse. I figure something external in your local dev environment must be getting it to work?
Hi Andy - I think this is due to a recent change in jscodeshift. I've logged an issue there; if I haven't heard within the next day or so I'll add a stripped version of the transform here. Thanks for reporting this!
Personally, I worked around this with
npm install jscodeshift@0.3.20
but we definitely should fix this generally.
Updated strict-type-args.js
to stripped version (original is in a src
subdir - see here), so should run fine now. Let's revisit if jscodeshift
makes it possible to pick up colocated .babelrc
s.
jscodeshift v0.3.26 removes type annotations form the transformer again. Sorry!
I just installed latest jscodeshift today.
jscodeshift: 0.3.25
I get a bunch of errors like this: