Is this project still being maintained?

[fmr]

Hi @brysgo,

I'm just wondering whether this project was still being maintained. I like the approach you have taken here and I haven't seen another project come close to solving multiple transforms elegantly.

If it's no longer being maintained, are there alternatives you know of that let you do multiple transforms easily?

Cheers

[brysgo]

@fmr I haven't touched this project because no one was interested in it. I would love to make it a thing if you have a use for it.

[brysgo]

Just updated the deps and enabled greenkeeper, should be okay to use 🚀

[brysgo]

(Would love to see how you are using it, and maybe get some good examples for the repo)

[fmr]

@brysgo Thanks for the response!

I've used it to apply multiple transforms successfully.

Here's what I liked about it:

• I'm able to apply multiple transforms in sequence to any number of files
• It's easy to whitelist paths to be transformed, both project-wide and for each transform
• I like how it reports results because of the how each transform should be written

What I didn't quite understand was:

• What was the jscodemigrate deps meant to do exactly? How should it look for transforms? Should it be configurable?

• When generating new codemods, why use timestamps for prefixes instead of a simple sequence?

• How can we effectively leverage existing transforms without having to rewrite them to match the function signature for jscodemigrate's codemods?

  • For example, how can I leverage the codemods provided by reactjs/react-codemod or cpojer/js-codemod without writing my own version of the scripts they've already written? (code mod their codemods? Or is that too meta?)

Apologies for the verbosity. I've also created a sample repo here (sorry for the quality, I created one as quick as I could): https://github.com/fmr/codemigrations

[brysgo]

•
What was the jscodemigrate deps meant to do exactly? How should it look for transforms? Should it be configurable?

You'll need to be more specific about it being configurable, but what it is meant to do is allow npm dependencies to publish codemods for API changes. When you run the deps subcommand, it finds code migrations marked as API changes and brings them into your codemigration folder.

•
When generating new codemods, why use timestamps for prefixes instead of a simple sequence?

Great question, this is to provide granularity for large teams, but might be unnecessary. I would be open to supporting alternative methods.

•
How can we effectively leverage existing transforms without having to rewrite them to match the function signature for jscodemigrate's codemods ?
• For example, how can I leverage the codemods provided by reactjs/react-codemod or cpojer/js-codemod without writing my own version of the scripts they've already written? (code mod their codemods? Or is that too meta?)

I love this idea, we should build it in. Could be a subcommand, like maybe import.

Thank you for taking the time on this, I will look at your examples at some point today.