Good practices on child Rmds

I find myself often creating a variety of RMarkdown Notebooks for various EDA topics and then want to include those in a master document, sometimes for the output though occasionally just for the processing elements. When using child documents I hit the problem that each of my notebooks uses a setup chunk to do library loading, which causes the master document to fail. Can anyone share their usage of child documents? I'm specifically wondering if I should bother with child documents and instead be looking at either bookdown for the combine-a-couple-of-notebooks-output-into-one problem or packages for the I-need-access-to-the-bit-of-processing-I-did-elsewhere.

Appreciate any stories or thoughts on the topic!