ast-grep VS git-xargs

This article illustrates the usage of ast-grep, a tool designed to locate and substitute patterns in your codebase, towards easing your migration to React 19.

This looks great, thanks for building and sharing it.

Interested folks may also want to check out ast-grep:

https://github.com/ast-grep/ast-grep

ast-grep is a command-line tool that lets you search and transform code written in many programming languages using abstract syntax trees (ASTs). ASTs are data structures that capture the syntactic and semantic structure of source code. With ast-grep, you can write patterns as if you are writing ordinary code, and it will match all code that has the same syntactical structure. And if you need more power, you can use YAML, a rule system that allows you to write more sophisticated linting rules or code modifications.

I really like this - it means the tool is available to people with familiarity of any of those four distribution mechanisms.

You can also download pre-built binaries from their releases page: https://github.com/ast-grep/ast-grep/releases/tag/0.14.2

On top of that, they offer API bindings for it in three different languages:

- Rust (not yet stable): https://docs.rs/ast-grep-core/latest/ast_grep_core/

- JavaScript/TypeScript: https://ast-grep.github.io/guide/api-usage/js-api.html

- Python: https://ast-grep.github.io/guide/api-usage/py-api.html

It's rare to see a tool/library offer this depth of language support out of the box.

Is there an open source library that does this? Maybe something on top of ast-grep

No problem, I had the same question just the other day. There is also git-xargs https://github.com/gruntwork-io/git-xargs

As mentioned earlier, try https://github.com/gruntwork-io/git-xargs, no need to reinvent the wheel!

I've looked for a solution to bitbucket and github but found something only for github that I'm yet to test (https://github.com/gruntwork-io/git-xargs). Other solution I thought about, that could work with bitbucket and github, is holding a script in a bucket or something and tell each repository's pipeline configuration to download and run it at some point.

You could try https://github.com/gruntwork-io/git-xargs

One problem with multi-repo is when you have to do service across a whole infrastructure (or large segments). Like patching. It's very very helpful to have a tool like https://github.com/gruntwork-io/git-xargs to help automate these things, where possible. You still end up with a crapload of PR's. So then it's helpful to have a streamlined review process for when you need to batch review PRs for a large change like this.