I know this will sound like a Luddite's opinion, but as soon as you need npm for your project, because of a technical decision one has made, you've introduced d

I know this will sound like a Luddite's opinion, but as soon as you need npm for your project, because of a technical decision one has made, you've introduced difficult to remove complexity. This is unfortunately at odds with what any reasonable software manager can tolerate, because developers on a team will introduce regressions, so you need to be able to test changes. I don't think web development has in any meaningful way progressed past manually choosing dependencies per-page with CDN'ized resources. When one chooses to rely on a package manager, you've separated yourself one significant degree from understanding exactly what is loaded on a page, which by necessity requires additional tooling to combat resource consumption growth. Any experienced software developer knows from having studied highly performant, widely used software that the fastest software is the software that does nothing. As haxiomic mentioned, if a library tells you its "blazing fast" you're being peddled to.