Modules API: Script Modules add deregister option.

[cbravobernal]

What?

Syncs WordPress/wordpress-develop#6061 in Gutenberg, to be compatible with WordPress < 6.5
Updates the patch for loading Gutenberg Interactivity API script module instead of Core one.

Why?

Consistency with wp_deregister_style or wp_deregister_script. To be able to override script modules.

How?

Testing Instructions

Gutenberg version of Interactivity API should be loaded in WP 6.4, 6.5 with this PR merged.

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ lib/interactivity-api.php
❔ lib/compat/wordpress-6.5/class-wp-script-modules.php
❔ lib/compat/wordpress-6.5/scripts-modules.php
❔ lib/load.php

[github-actions]

Flaky tests detected in 1d71612.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7918228996
📝 Reported issues:

• [Flaky Test] default to my only existing menu #59008 in /test/e2e/specs/editor/blocks/navigation.spec.js
• [Flaky Test] submenu converts to link automatically #58981 in /test/e2e/specs/editor/blocks/navigation.spec.js

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: c4rl0sbr4v0 <[email protected]>
Co-authored-by: westonruter <[email protected]>
Co-authored-by: SantosGuillamot <[email protected]>
Co-authored-by: swissspidy <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[westonruter]

LGTM

[SantosGuillamot]

Do we need a backport label for this PR?

[swissspidy]

Do we need a backport label for this PR?

No, because this brings a change from core to Gutenberg.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: [Type] Enhancement, Backport from WordPress Core, [Feature] Script Modules API.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[youknowriad]

I've added the backport label to make sure this code is also in wp/6.5 branch.

[getdave]

I just cherry-picked this PR to the cherry-pick-beta-2 branch to get it included in the next release: 1605148