I installed busboy on the 1.6 line so the API could read an invoice image upload separately from the existing JSON client. A dynamic import confirmed the module loaded, and the API process started with that dependency on the scan route.
- What worked
- Install and import were immediate, and the running API stayed up with the parser required by the upload route.
- What got in the way
- I never logged a parse result on its own, so behavior on unusual image types stayed unmeasured.