-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when running rename-unsafe-lifecycles #254
Comments
Could you try to isolate what file this happened on? If you could make a git repo with a reduced usecase, that would be excellent. Just to be sure that it isn’t related to your own dependencies, would you also try running this from outside your project? ie- instead of |
Ahh it seems to not like |
Very helpful, thank you! I'll have a look this weekend. |
@threepointone Did you ever solve this? I have a similar problem in a codemod I am writing where it chokes on the dynamic import. Not using React.lazy, but same syntax with loadable:
|
I'm not doing any active development on this, but I'd be happy to review and land a PR with a fix. |
Hey, not sure if related, but also getting a similar error |
@sterlu I had the same By telling the codemod to treat the code as Typescript it worked though. |
try |
Seeing this error when running rename-unsafe-lifecycles:
The text was updated successfully, but these errors were encountered: