Yeah, but the OP was about how many files there were in the project. And none of what you've mentioned here has any significant effect on how many files there would be in a project.

Though I do think probably my style of coding probably results in fewer lines of imports than many coders. I tend to eschew dependencies fairly radically. "A little copying is better than a little dependency" and all that. And also, my language of choice is Go, which doesn't allow importing individual things from a package the way, say, Java does. An import imports a package in Go. Just looking at that "biggest thing I've ever made", the most imports I have in any one file in my entire codebase is 18.

for f in $(find . -iname '*.go') ; do grep '^ "' "${f}" | wc -l | tr -d '\n' ; echo ' ' "${f}" ; done | sort -n

(Go syntax for imports generally adds a couple of lines in each file, so 18 imports would typically be 20 lines of code. And then there's usually a blank line after that before other code starts. You know how it is.)

And the total number of lines of just imports (including the two extra lines per import statement and blank line before other code starts) in my whole project is 1002 in a codebase that cloc calls 25693 lines and wc -l calls 28543 lines. So, like 3.37% to 3.351% of the codebase is imports. Oh, and the whole repo is 136 files.

(Full disclosure, there's a tiny bit of non-Go code in my project and I'm omitting all that in the above. A little HTML/JS/CSS here, a little GLSL there. And what I'm writing is a language, so I've got some code in my own language in the repo. Also, there's no vendored code in my repo or anything, so every character of what I'm talking about above was at one point a keystroke on my keyboard.)

Could be. I’m a build engineer so need to know enough about every language to build it. Luckily I was able to drop that as “will not support” (we’re mostly a Java shop, with Python, nodejs, and a few less common choices)