⓿ dependencies!
0dependencies.dev
0dependencies.dev
<link href="https://fonts.googleapis.com/css?family=Source+Serif+Pro" rel="stylesheet">Google Fonts is a convenience (one with a cost), not a requirement for being able to use a specific font on your page.
A more moderate recommendation would be a request to audit your dependencies and keep the transitive dependency bloat to a minimum.
Ideally libraries do have dependencies (you don't want every author re-rolling filesystem, network, crypto, etc.). Transitive dependencies should look like the bedrock packages for the language: well-supported, well-vetted, and have lots of eyeballs on them.
You don't need left-pad, but you probably don't want your own implementation of byteorder.
[](https://0depen...
The closest thing I've seen to do "zero dependencies" is esbuild, even then, last time I checked it has one dependencies in go.mod I think for old version's compatibility reason
What certain is, like the other commenter said, I believe in minimizing dependencies... not zero dependencies
Another nitpick: I hate the usage of `⓿` character. I wonder how this will be read by screenreader...
It gets casefolded to a 0.
0 runtime dependencies though is another story - very helpful in deployments where your package manager doesn't solve it.
Looking at the page it seems to more target towards library writers, if you draw the line at the programming language it's certainly possible to write useful libraries with no dependencies.
You can provide your own freestanding portion of libc & crt0 if using C, then if desired use those to write your own memory management (`malloc`, `calloc`, `realloc`, and `free`), then use those to write the rest of your own libc.