wp-build: Deregister script modules before re-registering

[scruffian]

What?

Follow-up to #75705. Adds wp_deregister_script_module() before wp_register_script_module() in the auto-generated module registration template.

Why?

#75705 removed the remove_action( 'wp_default_scripts', 'wp_default_script_modules' ) line to fix issues with third-party plugins using wp-build without Gutenberg activated. However, this caused a regression: wp_register_script_module() does not override existing registrations, so Gutenberg's bundled module versions are silently ignored in favor of Core's.

This is a problem for any module where Gutenberg's version differs from Core's. For example, the playlist block's view script module bundles additional dependencies (waveform player) that aren't in Core's version. With Core's version being served instead, the relative import to the waveform utilities fails silently and the player doesn't render on the frontend.

How?

Calls wp_deregister_script_module() before each wp_register_script_module() call. This is more targeted than the previous approach of removing Core's entire wp_default_script_modules action:

• Core's modules are registered normally
• The plugin explicitly overrides only the modules it ships
• Third-party plugins using wp-build without Gutenberg still work correctly

Testing Instructions

1. Activate Gutenberg
2. Create a post with a block that uses a viewScriptModule (e.g., the playlist block if available, or any block with interactivity)
3. View the post on the frontend
4. Open browser DevTools → Network tab
5. Verify the script module loads from the Gutenberg plugin's build/modules/ path, not from wp-includes/js/dist/script-modules/

🤖 Generated with Claude Code

[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: scruffian <scruffian@git.wordpress.org>
Co-authored-by: youknowriad <youknowriad@git.wordpress.org>

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

[Copilot]

Pull request overview

This PR updates the wp-build PHP module-registration template to ensure Gutenberg’s bundled script modules reliably override WordPress Core’s default script module registrations when running as a plugin.

Changes:

• Deregisters a script module handle before re-registering it during module registration.
• Adds inline documentation explaining why deregistration is necessary to override Core’s default modules.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

{{PREFIX}}_register_script_modules() is attached to wp_default_scripts, which passes a WP_Scripts argument. Because the callback currently declares no parameters, this can trigger an ArgumentCountError on PHP 8+ when the action runs. Align this template with script-registration.php.template by accepting the $scripts parameter (even if unused) or explicitly setting add_action( ..., 10, 0 ) to avoid extra args being passed.

[youknowriad]

This is probably a regression after #75705 (that explains why that default script registration was needed). The approach in this PR is better though, I think it doesn't impact third-parties like the previous approach.

cc @dhasilva

[github-actions]

I just cherry-picked this PR to the wp/7.0 branch to get it included in the next release: 024f173