viewScriptModule is also being loaded in the block editor

[juanmaguitar]

Description

viewScriptModule file defined in the block.json is meant to be loaded only in the frontend when the block is displayed but right now is also being loaded in the block editor

Step-by-step reproduction instructions

1. Go to the plugins folder of a WordPress instance
2. Run npx @wordpress/create-block@latest demo-iapi-block --template @wordpress/create-block-interactive-template to quickly create a block with a viewScriptModule definition
3. Enter into that folder (cd demo-iapi-block), install dependencies (npm install) and run the build process (npm run build)
4. Activate the plugin, open any post and insert Demo Iapi Block
5. Save and reload the Block Editor

Current behaviour

view.js defined as viewScriptModule is loaded in the Block Editor

Expected behaviour

view.js defined as viewScriptModule should not be loaded in the Block Editor. It should only be loaded in the frontend when the block is displayed.

Screenshots, screen recording, code snippet

No response

Environment info

• WP Version: 6.8.3
• Tested with WordPress Studio and wp-env
• No other plugins activated

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[SirLouen]

Reproduction Report

Description

✅ This report validates that the issue can be reproduced.

Environment

• WordPress: 6.9-beta2-61080-src
• PHP: 8.2.29
• Server: nginx/1.29.3
• Database: mysqli (Server: 8.4.7 / Client: mysqlnd 8.2.29)
• Browser: Chrome 141.0.0.0
• OS: Windows 10/11
• Theme: Twenty Twenty-Five 1.3
• MU Plugins: None activated
• Plugins:
  • Demo Iapi Block 0.1.0
  • Gutenberg 22.0.0-rc.1
  • Test Reports 1.2.0

Actual Results

1. ✅ Error condition occurs (reproduced).

Additional Notes

The situation is the following:
script modules is being hooked into both front end and back end here:
https://github.com/wordpress/wordpress-develop/blob/bafd51b8ff87c8f51357e01def21489dc38e2474/src/wp-settings.php#L429

Originally, this was introduced two years ago here as part of the ES Modules support 57503
WordPress/wordpress-develop#5945 (comment)

So despite of the original enqueue which gave the information to the docs was only loading script modules in the front, this change made the script modules to enqueue also in the backend because the add_hooks was not discriminating the type of incoming script.

So being loaded in the front-end seems like a side-effect. Maybe this could be either fixed or improved in the docs given the new scenario.