Update dependency @wordpress/server-side-render to v1.2.0

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
@wordpress/server-side-render	devDependencies	minor	1.1.0 -> 1.2.0

---

Release Notes

WordPress/gutenberg

v1.2.0

Compare Source

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

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

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 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. View repository job log here.

[swissspidy]

Some new placeholder components have been added: https://github.com/WordPress/gutenberg/blob/02c5f3950dda05ffbba532d285e58be9232c0acf/packages/server-side-render/CHANGELOG.md

Looks like there are some actual test failures

[swissspidy]

WordPress/gutenberg#16133 broke things apparently 😞

[swissspidy]

We're polyfilling wp.serverSideRender in case someone is using the Latest Stories block without using up-to-date Gutenberg (because it used to be in wp.components before). The code for that is very straightforward:

amp-wp/assets/src/polyfills/wp-server-side-render.js

Lines 4 to 8 in 60d5b75

	import * as serverSideRender from '@wordpress/server-side-render';
	window.wp = window.wp || {};
	window.wp.serverSideRender = serverSideRender;

@wordpress/server-side-render itself shims window.wp.components.ServerSideRender and emits a deprecated call in case anyone should access that.

However, this now causes issues with our Babel transpiling.

To reproduce:

1. Checkout this branch / update the package
2. Build plugin
3. Make sure Gutenberg is not active
4. Visit block editor
5. See error

@barklund @miina Any ideas regarding this?

[barklund]

1. Checkout this branch / update the package

This branch, right?

2. Build plugin
3. Make sure Gutenberg is not active
4. Visit block editor
5. See error

Which error is that exactly?

I'm not sure my local setup is 100% correct, but I "only" see an error about Warning: Unsafe lifecycle methods were found within a strict-mode tree.

Can you help me replicate the issue?

[swissspidy]

Okay I am failing to replicate now 🤦‍♂ but it was this error:

TypeError: Cannot set property ServerSideRender of #<Object> which has only a getter
      at Module.<anonymous> (../../http:/localhost:8890/wp-content/plugins/amp/assets/js/wp-server-side-render.js?ver=1.2.3-alpha:3:689)
      at n (../../http:/localhost:8890/wp-content/plugins/amp/assets/js/wp-server-side-render.js?ver=1.2.3-alpha:1:110)
      at ../../http:/localhost:8890/wp-content/plugins/amp/assets/js/wp-server-side-render.js?ver=1.2.3-alpha:1:902
      at ../../http:/localhost:8890/wp-content/plugins/amp/assets/js/wp-server-side-render.js?ver=1.2.3-alpha:1:912
      at Suite.it (specs/block-editor/amp-toggle.js:19:2)

[forking-renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (1.2.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.