I think targeting no JS at all is much more impactful to the overall experience of web development. Reaching for it only when HTML+CSS have failed you is the original intent. Server-side rendering can take you really far if you are patient and creative.

NPM/Node is at the heart of my displeasure with JS. I don't mind JS in the browser when done tastefully. But I don't think it makes much sense outside of the DOM. As another comment noted, you often have to go dig through CDNs and hack at URLs to get the actual JS files for non-insane hosting models (i.e., statically from the same machine that hosts everything else). The notion that I need a CDN to serve a few kilobytes of source for anything short of netflix.com is absolutely insane.

I would advocate starting your next web project using 0 lines of JS, even if you intend to use the full USS Enterprise to build it out for prod. See how far you can get with just HTML & CSS. Consider that anything proximal to layout/style/art/etc. is entirely within this box. Javascript is not going to save you from an art problem. It can only make it worse.