refactor: use serialize-javascript instead own implementation

[alexander-akait]

Notable Changes

1. serialize-javascript more stable and support many features (see https://github.com/yahoo/serialize-javascript/blob/master/index.js#L14 https://github.com/yahoo/serialize-javascript/blob/master/index.js#L90 and etc)
2. Reducing the code, serialization out of scope plugin code and should be separate package

Issues

• None

[michael-ciniawsky]

Nothing against this change in particular and if serialization is unavoidable, but I would like to traige eventual possibilities to avoid serialization for options altogether if possible (maybe it isn't).

1. webpack uses an ident, maybe we can use a similiar approach
2. https://github.com/rvagg/node-worker-farm#exportedmethods but not 💯 if this is helpful here (didn't tested it out yet)

[alexander-akait]

@michael-ciniawsky ident don't contain function, regex and date, we can't use this as cache key

[michael-ciniawsky]

// 'use strict' => this === undefined (Clean Scope)
// Safer for possible security issues, albeit not critical at all here 
options = new Function(`'use strict'\nreturn ${options}`)()

callback(null, minify(options));

[michael-ciniawsky]

cacheEntriesListKeys => cacheKeys && serializedCacheEntry => cacheEntry

[michael-ciniawsky]

Why did this change ? It's the same as in #190 I just can't reason about it 😛

[alexander-akait]

@michael-ciniawsky oh yep 👍

[alexander-akait]

@michael-ciniawsky done

[michael-ciniawsky]

workerOptions => options (Just reassign options below please)

[alexander-akait]

@michael-ciniawsky eslint throw problem about no-param-reassign, but it is not make sense here.

[michael-ciniawsky]

eslint-disable-next-line ? 🙃

[alexander-akait]

@michael-ciniawsky done 👍