[bryanrasmussen]

I totally agree with this except - just when I was done with reading this thread I went back to the project I was on and I noticed there was some file in the root of the project red in VSCode so I go look at it, it's a JSConfig.json wtf is that I don't remember that config.

It says

{ "compilerOptions": { "baseUrl": "./" }, "exclude": [ "node_modules" ] }

I go google what it is, seems to be some VSCode thing added automatically maybe? https://code.visualstudio.com/docs/languages/jsconfig

but VSCode thinks it should be marked red, something is wrong with this config file I have no familiarity with. grrr.

anyway - I think at some point, especially on projects with lots of devs and lots of tooling, you look at the root and like art you know what you like or don't like and sometimes there will be a feeling that there are just too many files here for configuring stuff! But probably that indicates some other underlying problem, not a problem with having config files in itself.

[ralphstodomingo]

Yeah - I think that's a cue pointing to you that your understanding of the project at hand may be lacking in some regard. I usually listen to that signal and learn the heck out of the current tooling whose config I see on the root before proceeding with the subdirectories.

That feeling of mild anxiety in not knowing why these files are there can be useful, is all I'm saying.

[bryanrasmussen]

yeah or it's a cue that someone using VSCode created a JSConfig.json checked it in and it got pulled by the latest git pull.