Vanilla JS nowadays means not using a framework, in yesteryears it meant not using jQuery, in either case, it doesn't preclude from having dependencies.

to be fair, in case the dependencies are pegged to specific known-good versions and are bundled into one or a few files then two concerns with dependencies go away, namely, insanely deep and wide file system trees and the lingering danger of any one of hundreds of software titles getting malware-ized. One could even add that it's probably a good idea to prefer tried-and-tested existing software over writing everything from scratch.

Not OP, but in my opinion:

When I am reading through the source code of somebodies personal project, it's absolutely amazing to:

- see how to do X in discernible, concise, modern JavaScript

- follow along significant architectural decisions

- watch a web API in action, not a specialized abstraction that will necessarily hide some capabilities

That being said: This project doesn't offer much in that regard. It's hard to read and makes little use of modern JavaScript.