Update Newspack blocks to v1.37.1

[noahtallen]

Changes proposed in this Pull Request

Bump newspack blocks to v1.37.1 and resolve peer dependency warnings via .yarnrc.yml.

Releasing to npm

Here's how I did the release to npm:

1. Cloned the newspack blocks repo
2. Checked out the commit tagged with the 1.37 release
3. Changed the "name" field in package.json to include @automattic/ as a prefix
4. Removed the private: true field in package.json.
5. Ran the following commands:

npm ci
npm run clean
NODE_ENV=production npm run build

npm publish

Testing instructions

1. Sync the build to your sandbox (install-plugin.sh etk update/newspack-blocks-1.37)
2. Load the editor in a sandboxed site, and verify the ETK version in the "more menu" dropdown matches the version on your sandbox.
3. Smoke test inserting and using the newspack blocks.

[github-actions]

Link to Calypso live: https://calypso.live?image=registry.a8c.com/calypso/app:build-14537
Link to Jetpack Cloud live: https://calypso.live?image=registry.a8c.com/calypso/app:build-14537&env=jetpack

[matticbot]

This PR modifies the release build for editing-toolkit

To test your changes on WordPress.com, run install-plugin.sh editing-toolkit update/newspack-blocks-1.37 on your sandbox.

To deploy your changes after merging, see the documentation: PCYsg-mMA-p2

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~17 bytes removed 📉 [gzipped])

name                 parsed_size           gzip_size
entry-gutenboarding        -77 B  (-0.0%)      -17 B  (-0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Async-loaded Components (~15 bytes removed 📉 [gzipped])

name                                            parsed_size           gzip_size
async-load-design-wordpress-components-gallery        -77 B  (-0.0%)      -15 B  (-0.0%)
async-load-block-editor                               -77 B  (-0.0%)      -15 B  (-0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[fullofcaffeine]

Hmm, do you know why api-fetch peer-depends on react-native? 🤔

[noahtallen]

Yes, there is one wp package which has react-native as a peer dependency, and that causes everything else which uses that package to show a warning. Since a lot of wp packages depend on that package but do not include react-native, yarn says that the peer dependency requirements are not met. Adding it to the peer dependencies in this file basically indicates to yarn that we (the calypso repo) will provide that peer dependency, thus resolving the peer dep requirement.

That said, I think this issue doesn't exist with newer versions of WP packages, so it's possible we can remove it

[noahtallen]

I've just double checked. It hasn't been published yet, but WordPress/gutenberg#34687 will resolve this issue. The exact problem is:

• react-native-url-polyfill is added by @wordpress/url
• react-native-url-polyfill has a peer dep on react-native, which isn't provided by @wordpress/url
• Everything else including @wordpress/url (such as @wordpress/api-fetch) now has an invalid peer dependency requirement.
• These are fulfilled by adding react-native as a peer dep to each package depending on @wordpress/url, and then providing react-native at the top level ourselves

[fullofcaffeine]

Tested well from the sandbox. Some unrelated tests are failing and I re-triggered them just in case.

[dkoo]

Smoke test looks good! 👍