why is the gitlab-ci.yaml lumped in here? that's got nothing to do with the JS ecosystem. I can see why it'd be annoying to have all these files but it's because each tool for the most part does one thing. I'd rather a set of tools that can be switched out whenever then be stuck with a single tool forever because it's to difficult to switch out.
Discussion
More generally so much damned config as a dev to deal with
The number of layers of leaky abstractions that have to be understood and managed is too damn high. 
yeah for sure. i understand that. i think all the tools should have an init command to make a "good enough" config from the start. or just don't allow config. like prettier initially didn't really have any config. that was the point.