GrayStrider

I imagine the problem may have something to do with Vuex store recalculating on every change? Perhaps, something like immer would help?

@pokeriscute "Benefits" section of an official [introduction](https://immerjs.github.io/immer/docs/introduction) outlines the use cases fairly well! And try to stay on topic when commenting on issues next time; use Discord or Stack Overflow...

> @AlexisNava > > Try this in your app.test > > ``` > const request = require('supertest'); > const app = require('../app'); > describe('App Request', () => { > test('should...

``` afterAll(async () => { await sleep(500) }) ``` works too.

> If accepted, it would require solution for serving static assets from public directory. At the moment, content usually pre-built like css (from scss) could not be used when started...

Nevermind, found a much better option, one sec

Are there any other adjustments needs to be made?

Now that #235 is merged, would be nice to actually update those `any` types? I'm not exactly sure how this whole thing works, should I make any other improvements, or...

Given that #218 seems to be popular, I don't think this is gonna fly for the same reasons. The project seems to position itself as a "starter", not as "boilerplate"....

Seem to repeat many edits from #232 as well, we really need some merges or comments, @peterblazejewicz Perhaps, move `isKnownProvider` into separate PR for review? @mateja176 It's a new feature...