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

Takes a package name and a dest path. This way we can more eassily change the
layout and it will error out on package name typos or missing packages.

Add a scope so we don't have to care about naming conflicts
and set the verison to 0.1.0 since we don't have a stable API yet.

Instead of hardcoding the paths of the node_modules directory we use the node-resolve
plugin of rollup to find the root of the corresponding JS package and calcucate a path from
there.

Resolving a package requires calling an async function, so we have to use await in the rollup config.
Luckily rollup supports configs wrapped in a promise, so we just have to wrap it in a function which returns
a promise.

Also add test for the demo

Bekerle, Patrizio authored 5 years ago and Reiter, Christoph committed 4 years ago

Initial commit with basic KnowledgeBaseWebPageElementView web component scaffold including authentication