---
# System prepended metadata

title: CodeMods infrastructure
tags: [pitch]

---

---
robots: noindex, nofollow
tags: pitch
---
For instructions on shaping a project see here: [Shaping a Project](/kX02SXVbS6KzMOQd56i6Cg)

# CodeMods infrastructure

### Problem
Currently codemods have all the structure that is strictly necessary to run. It needs fine tuning in the form of logging, error handling, and in depth how to's/examples.

### Appetite
3 weeks. Getting codemods in a state so that not only can they run but that we can get feedback on them is important. Once we begin to get feedback we can start to implement new features.

### Solution
1. Make codemods async using promises.
2. Add callbacks to handle logging and error handling.
3. Write 2-3 example codemods that handle simple to complex cases.

### Risks (Rabbit holes)
It's possible to go too deep into logging. Only log what's necessary to start and build from there. Don't worry too much about writing verbose examples. They should be clear and too the point. Don't over explain.

### Out of scope (No-gos)
There are lots of features that will be great to have in the future that we shouldn't add. We don't need to write logs to a file or have the logs update inline just yet.