Paul Tiedtke

I think this PR should fix the problem but it's not released yet. https://github.com/webpack-contrib/mini-css-extract-plugin/pull/422

It was directly released after I posted my comment. So you can use version `0.8.0` and set the options documented in the README.

**Feature Request:** Subscribing to relation changes It should be possible to subscribe to relation changes without using the `dummy` workaround of Prisma 1. https://github.com/prisma/prisma/blob/master/docs/1.2/04-Reference/03-Prisma-API/05-Subscriptions.md#subscribing-to-relation-changes

I've recently asked in slack when we can expect to get subscription support. This was the answer by Nikokas Burk (Prisma): > There's no official timeline but I don't except...

@Maxhodges What I love on Prisma 1 is that I can just subscribe to database changes and can redirect the connection directly to the subscription of my own graphql server....

Or introduce another one for health checks and if one of them is true the rest API will be enabled. WDYT? Edit: but then we would still have the version...

Because it's just one option and isn't granular anymore it makes sense to just have a single variable. I mean this variable change for REST APIs was breaking anyway.

Here is a discussion I had about this topic - it may have some helpful information. But please note that it's a bit kubernetes specific. https://community.jitsi.org/t/scale-videobridge-inside-kubernetes/20527

I'm wondering why this happens because [the PR](https://github.com/jitsi/jitsi-videobridge/pull/1785) is not merged yet.

@saghul Can it be that the `artifactId` has changed so that the dependency is not getting installed? Unfortunately I don't really know that much about Java and Maven setups. ###...