Prepare a batch of releases.

[aomarks]

• dom5@3.0.1
• @polymer/tools-common@2.0.1
• polymer-analyzer@3.0.2
• polymer-project-config@4.0.2
• browser-capabilities@1.1.1
• @polymer/esm-amd-loader@1.0.2
• polymer-bundler@4.0.2
• polymer-build@3.0.4
• polyserve@0.27.12
• wct-sauce@2.0.3
• polymer-linter@3.0.1
• polymer-editor-service@2.2.2
• polymer-cli@1.7.7

[hastebrot]

No updated version of polyserve? I think it includes fixes to NPM warnings.

[aomarks]

No updated version of polyserve? I think it includes fixes to NPM warnings.

Oh good point, I'll add the packages with NPM audit fixes. Was only looking at CHANGELOGs.

[usergenic]

LGTM

[TimvdLippe]

Awesome thanks!

[aomarks]

All releases done! @TimvdLippe how are we looking with the NPM audit issues now?

[hastebrot]

After the NPM packages with the NPM audit fixes were released yarn still complains. I wonder why this is, e.g. polyserve should automatically use the latest polymer-build release (with the audit fixes).

❯ yarn install
yarn install v1.7.0
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning wct-browser-legacy > sinon > formatio@1.1.1: This package is unmaintained. Use @sinonjs/formatio instead
warning web-component-tester > sinon > formatio@1.2.0: This package is unmaintained. Use @sinonjs/formatio instead
warning web-component-tester > nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "polyserve > polymer-build > @babel/plugin-transform-classes@7.0.0-beta.35" has incorrect peer dependency "@babel/core@7.0.0-beta.35".
warning "polyserve > polymer-project-config@4.0.2" has unmet peer dependency "polymer-analyzer@^3.0.1".
[4/4] 📃  Building fresh packages...
success Saved lockfile.

Update: Maybe this is also caused by my minimalistic setup (I only use polyserve and web-component-tester and wct-browser-legacy). When I also add polymer-analyzer one of the warnings goes away.

[TimvdLippe]

@hastebrot wct-browser-legacy and web-component-tester still have vulnerabilities, I am working on fixing them.

@aomarks Audit issues in all other packages are resolved 🎉 However, the lockfiles are broken again, as the npm run nuke script is not working correctly. See #448 (comment) for the fix.

[web-padawan]

@TimvdLippe can I ask you to also look at Polymer/polymer-modulizer#452 later if you have time?
It also contains a fix for some vulnerabilities issues in modulizer.

[TimvdLippe]

@web-padawan I think we need to import modulizer in this repository to make this all a lot easier. Will ping the team to see what they think

[web-padawan]

@TimvdLippe that's a valid point. I recall some PR to import polymer-workspaces (used by modulizer) which has been postponed.

At least it would be nice to have another modulizer release before importing it here, as there are at least 2 merged but not released fixes.