It always seems like the button is missing when loading the page and
expecting the button there based on experience.

Instead of going through the rollup plugin. Turns out the rollup plugin
api shouldn't be used outside of rollup.

Ideally this should give us the same path resolution anyway, even though it's
potentially a different implementation.

Reset value attribute to really make sure it is empty and will trigger a change event when it is set again with the previous value

It tries to call a resolve method which doesn't exist somehow.
Mock it to get things back to the old behaviour.

Fixes #22

chore(deps): update dependency eslint-plugin-jsdoc to v33

See merge request !48

app-shell: Support the new scoped elements registry polyfill

See merge request !50

Register the activity properly and create a scoped element if the API is there.

One all bugs are fixed upstream this should allow us to switch to lit v2
without any further changes.

chore(deps): lock file maintenance

See merge request !49

https://docs.renovatebot.com/configuration-options/#lockfilemaintenance

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.

showcase: Fix syntax highlighting

See merge request !47

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

Make the toolkit-showcase package part of the main workspace package

See merge request !46

It's confusing that there are two lock files in this repo and two
overlapping workspaces. Ideally everything should be in sync.

Switch from chai to @esm-bundle/chai

See merge request !44

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

file-handling: fix a dep cycle

See merge request !43

Make sure every package supports eslint and run in CI

See merge request !45