Skip to content
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

Investigate moving to jscodeshift, recast, or other mass-mutator #20

Open
JoshuaKGoldberg opened this issue Dec 15, 2018 · 0 comments
Open
Labels
area: architecture Changes to how the core of TypeStat works status: proposal needed Seems like a good idea, but needs a solid proposal for how to continue

Comments

@JoshuaKGoldberg
Copy link
Owner

JoshuaKGoldberg commented Dec 15, 2018

It added TypeScript support just after I started work on TypeStat. 😔

Can jscodeshift do what the automutate backend does already? As much as I like my own projects, it'd be nice to use what everyone else does.

@JoshuaKGoldberg JoshuaKGoldberg added status: proposal needed Seems like a good idea, but needs a solid proposal for how to continue area: architecture Changes to how the core of TypeStat works labels Dec 17, 2018
@JoshuaKGoldberg JoshuaKGoldberg changed the title Investigate moving to jscodeshift Investigate moving to jscodeshift or other mass-mutators Nov 16, 2019
@JoshuaKGoldberg JoshuaKGoldberg changed the title Investigate moving to jscodeshift or other mass-mutators Investigate moving to jscodeshift or other mass-mutator Nov 16, 2019
@JoshuaKGoldberg JoshuaKGoldberg changed the title Investigate moving to jscodeshift or other mass-mutator Investigate moving to jscodeshift, recast, or other mass-mutator Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: architecture Changes to how the core of TypeStat works status: proposal needed Seems like a good idea, but needs a solid proposal for how to continue
Projects
None yet
Development

No branches or pull requests

1 participant