I think I figured it out (?)
If I add a bundledDependencies array to my package.json, this problem goes away. I just need to be sure that every dependency that's being checked into the repo is included in the bundledDependencies array.
I would have figured this was a more common use case, however, so the fact that I had such a hard time finding anything on the subject makes me think I might be going about it the wrong way. More specifically, we are currently checking in these dependencies to avoid any issues when deploying to production, a better solution might be for us to switch to not checking the dependencies in and instead using npm shrinkwrap