Kirill Konshin

So far I came up with following fix: 1. Make sure `svg-sprite-loader` is not hoisted if you use yarn workspaces or similar, and it has fixed version `5.2.1` 2. Install...

Any updates? This is still an issue...

I guess even simple regex with `from` and `to` would be enough. Probably it may require path resolution though.

Why do you think it will cause performance overhead? You use node's coordinates to draw connections, so you should have access to node's properties, right? If this is true, just...

Bump!

I have tried with strength = 1  Also I tried negative strength. Did not help, nodes are still crowded in a corner after any data update.

Especially useful if you install ffmpeg via NPM: `npm install ffmpeg-cli` for example.

Each worker may receive own cache sub-directory, but then there would be a problem to merge all caches back to one (option 3, basically). And on subsequent runs single cache...

``` "jest": "25.1.0", "allure-jasmine": "^2.0.0-beta.6", "allure-js-commons": "^2.0.0-beta.6", ```

Any progress?