epszaw

So, as I can see the PR has been merged many time ago :) What do you think, @davidjgoss, is it necessary to provide `workerId` property to any envelope? Of...

So, I updated the PR up to the new messages API. Even if you won't decide to provide `workerId` everywhere – it's ready to merge with the current solution :)

@davidjgoss done 👍

Yay! 🙌

@ezhikov it's very simple. Look at other test a try to do the same. If you don't have any experience with unit testing and test tools, I highly recommend to...

@jondot we can build two files and define in `package.json` entries for `module` and `main`. Ofc, first file in `cjs` format and second in `es` module format.

I guess, it's better to solve the problem with locally written plugin. Base SVGO functionality shouldn't handle all the possible cases

@GreLI is here any activity? The last release was in October of 2019th. The most of pull requests is awaiting a lot of time.

@sayjeyhi it seems, that project is dead. I think, it is possible to make a fork and allow to users pass custom plugins.

@TrySound as I understood, in `svgo@2` is coming? Should I update this PR and plugin?