seeking some options to override a file included in a module included by a module. That is, I am building an app (A) that include lib (R) that includes lib (C). I need to make a VERY SMALL modification to a single method in one module in C. These changes are not generally applicable to the devs and users of C (so a PR doesn't make sense).

I can think of a couple crappy ways to do this:

1. fork C (C'), make the change, fork R (R') and change the package to include my C'. Include R' in A.
2. as part of my build for A, munge the file in the deep-included copy of C (the change is literally return true;) - file would be in A/R/node_modules/C/....

Long term, I'm working with the customer who is the target of the demo to create a means to identify their target as a use case and modify C's code to handle that case (there are lots of specific behaviors in C) as a PR.

Does anyone have any better ideas or suggestions on how to handle so that

• Syncing upstream updates aren't a nightmare and can be pulled fairly easily
• doesn't create a cryptic mess for my customer when they use my demo code (A)

Oh and R and C are both large-ish projects with lots of users and decent code velocity... hence why I'm keen to keep in sync with the upstream changes.