Dependencies

Dependencies are software libraries and tools that a piece of software requires to be present in order to function. Dependencies provide ready-to-use functionality but, as their name indicates, they are also liabilities. They take up space in memory, but perhaps more importantly, they can become inaccessible or change in incompatible ways, making the dependent piece of software difficult or even impossible to use.

If you choose to use HyperDoc, it becomes a dependency of your code. And HyperDoc's dependencies become your indirect dependencies. You should thus know what these dependencies are.

HyperDoc is implemented as two ASDF systems:

• hyperdoc contains just the code required to set up a HyperDoc. This is what your code will depend on even for users of your code that don't care about HyperDoc. Its direct and indirect dependencies are:
  (html-inspector-views/standard::👀dependencies (asdf:find-system "hyperdoc"))
• hyperdoc/explorer contains the code required to display and navigate a HyperDoc. This is what developers and users of your code need to load to actually profit from the HyperCode, but it does not become a dependency of your code. Its direct and indirect dependencies are:
  (html-inspector-views/standard::👀dependencies (asdf:find-system "hyperdoc/explorer"))