Add multiple styles/scripts with dependencies, version, etc. in block.json and provide examples in documentation

[troytempleman]

• Part of Block API #41236.

What problem does this address?

I see on the Metadata in block.json page that its possible to add front end, editor and shared styles/scripts in block.json. I also see you can add multiple scripts for each one of these, even with a mix of file names and previously registered script handles. For example, "style": [ "file:./style.css", "example-shared-style" ]. This is great as it eliminates the need to enqueue these with wp_enqueue_script and wp_enqueue_style in PHP.

However, its not clear to me if you can add an array of dependencies, version, etc. for each script, or if you still have to use wp_enqueue_script/wp_enqueue_style when that is needed. If not, it would be even better to add this option, as each script often have their own dependencies, version, etc. It would also be nice to see an example of how to do that.

What is your proposed solution?

Add the option to add multiple styles/scripts with dependencies, version, etc. in block.json (if not already possible) and provide examples of how to do so on the Metadata in block.json page (or elsewhere).

[gaambo]

That's a great point and it's the reason why I mostly register my block assets via wp_register_script and then only pass the handle in block.json: So I can define dependencies.
But I guess it's hard to think of a "simple" schema to define those in JSON.
I guess using @wordpress/scripts simplifies that a bit, because It creates an .asset.php file which has the dependencies and a version. In some old projects I'm still building all assets via Gulp and don't have that - so I manually define the dependencies and create a version based on filemtime.