More Accurate Dependencies

[aidan-epperly]

It has occurred to me that we are reliant on a number of d3 related repositories such as d3-simple-slider and d3-tip, but this is not reflected in the dependency graph. We may want to find a way to explicitly tell github that we use these things. I don't think the cdn (#34) affects this at all, but I think the dependency graph is a good thing to keep in mind for the future.

[LRWeber]

GitHub interprets dependencies based on requirement/manifest files.
https://docs.github.com/en/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems
Maybe there's some kind of file that is independent of any package manager that would still allow us to note such dependencies?

[LRWeber]

Technically, we could make a package.json file as used for npm to include this info. There would be no purpose to running any npm commands, but it would at least document the additional packages.

This could also open up the possibility of additional linters etc beyond just the python packages we use now.

On a related note, we should probably include python dependencies for both production and development in order to include the linters we are actively using.