[Create Block]: Add ability to pass a slug for the block name

[ryanwelcher]

What problem does this address?

Currently, when scaffolding a block with the @wordpress/create-block package, we can pass a slug to define the name of the plugin, which is also used as the name of the block. This was brought up in #41642 (comment)

npx @wordpress/create-block my-awesome-plugin

The command above would generate a plugin called 'my-awesome-plugin` with a block of the same name. There are many times that the name of the plugin will be different than the block.

What is your proposed solution?

Introduce a new CLI parameter called --block-name to allow the command to function as follows:

npx @wordpress/create-block my-awesome-plugin --block-name custom-block

[ryanwelcher]

Now that #41642 is merged, this parameter could be used to pass a series of names to allow scaffolding of multiple blocks at once

npx @wordpress/create-block --no-plugin --block-name custom-block-one,custom-block-two

[dgwyer]

Now that #41642 is merged, this parameter could be used to pass a series of names to allow scaffolding of multiple blocks at once

100% yes! I'm currently doing exactly this in a custom script I created. But I'd love to see it added as part of the @wordpress/create-block core script.

e.g. To create multiple blocks:

npx create-wp-block todo-list -b block1 block2 block3

https://github.com/dgwyer/create-wp-block

[gziolo]

I’m all in for adding support for multiple blocks. It might be quite challenging to achieve in the quick mode because there are a few CLI args that should differ between blocks:

https://github.com/WordPress/gutenberg/blob/a3c753d28ddb0972311e2da0136277626bdf832e/packages/create-block/lib/index.js#L40L50

namespace is the only CLI argument that we want to share and maybe category but slug, title, and short-desc should definitely differ between blocks and even often with the plugin.