In newer versions there is now a normal method for this which also supports
dynamically added components.

The static version is deprecated and removed in 2.0, so we need to port here.

Include the highlight.js css in all activities and move the
code css into the app, so it's defined where it is used.

This has proper support for rollup while providing the same API.

This is what open-wc recommends now and uses in their @open-wc/testing package

Importing the module itself adds a dependency on teh index which creates a cycle.
Reference the internal file instead.

This prevents eslint from traversing the parent directories. In
the case there was a conflicting eslint config in a parent directory it would
error out otherwise (like is the case in our apps)

Use "await JSONLD.getInstance()" instead

No longer needed

In theory this can replace all other API.

We can access that API without a token.

appending "#debug" to the URL enables it again. Not sure if this
the best mechanism, but better than spaming the console for now.