Update dependency @wordpress/build to v0.16.0

[matticbot]

This PR contains the following updates:

Package	Change	Age	Confidence
@wordpress/build (source)	0.14.0 → 0.16.0

---

Release Notes

WordPress/gutenberg (@​wordpress/build)

v0.16.0

Compare Source

v0.15.0

Compare Source

Bug Fixes

• Defer single-page admin import( "@​wordpress/boot" ) until DOMContentLoaded so the boot module evaluates after classic script dependencies have loaded (#​78136).

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 02:59 AM, on day 1 of the month ( * 0-2 1 * * ) in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the renovate/@wordpressbuild branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack renovate/@wordpressbuild

bin/jetpack-downloader test jetpack-mu-wpcom-plugin renovate/@wordpressbuild

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[simison]

FYI, WP Build looks to be missing some changelog entries, adding in:

• Build: update changelog WordPress/gutenberg#78807

[simison]

FYI v0.15.0 version had a bug which caused a revert of one feature and GB point-release:

• Revert "wp-build: Replace getter-based exports with data properties" WordPress/gutenberg#78917

Edit:

Nope, that was actually released as part of v.0.14.0, which Jetpack uses and seems to not be causing issues here.