This fixes a typescript problem and allows us to enable type checking
in the typescript-example package (by removing the ts-nocheck comment)

This is all very basic, building works, testing works,
but there are type checking errors which I don't know how
to fix.

Improvements welcome.

See #41

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.

While it's nice to have a fixed chrome version it slows down the yarn install,
downloads a lot of things, and the chrome version depends on various
system packages so one needss to have chromium installed anyway.

This means developers that want to work on tests need firefox and chdomium installed.

Sadly I couldn't find a way to make browsers optional in case the developer
only has one installed.

Use tdd in all cases to be more consisstend.
Also since last year we can use chai with rollup directly, so
do that everywhere instead of relying on karma-chai injecting
it in to the global scope.

We no logner use that library and the "qr-scanner" altternative turned out to
be better, so remove it completely.

With both being async it's hard to follow what would happen if both run at the same
time, so just prevent it and serialize start/stopping instead.

This makes sure the library version works with the server version.

Ideally we'd also want to check the version so we can error out if a too
old keycloak server is on the other side, but I don't see any public API changes
that would allow us to know if the library is too old.

Fixes #32

See #32

I couldn't find any breaking changes affecting us

It's a webpack plugin, so unlikely that it is used.

Neuber, Eugen Ramon authored 4 years ago and Bekerle, Patrizio committed 4 years ago

Activate Matomo logging only after user logged in successfully. Deactivate if user logs out.

Using lerna with npm breaks various npm commands such as "outodated"
etc.

Switch yarn with namespaces. lerna is only used to run commands on all
packages and maybe publish them etc. yarn 2.x has extra workspace features
like running commands for all packages, so with 2.0 we might also get
rid of lerna.