@wordpress/create-block 4.0.0 → 4.1.0

package/README.md

@@ -24,6 +24,8 @@ _(requires `node` version `14.0.0` or above, and `npm` version `6.14.4` or above
 
 It creates a WordPress plugin that you need to [install manually](https://wordpress.org/support/article/managing-plugins/#manual-plugin-installation).
 
+[Watch a video introduction to create-block on Learn.wordpress.org](https://learn.wordpress.org/tutorial/using-the-create-block-tool/)
+
 ## Usage
 
 The following command generates a project with PHP, JS, and CSS code for registering a block with a WordPress plugin.
@@ -87,7 +89,6 @@ $ npx @wordpress/create-block --help
 
 5. No plugin mode – it is also possible to scaffold only block files into the current directory.
 
-
 ```bash
 $ npx @wordpress/create-block --no-plugin
 ```
@@ -144,107 +145,7 @@ _Note: You don’t need to install or configure tools like [webpack](https://web
 
 ## External Project Templates
 
-Are you looking for a way to share your project configuration? Creating an external project template hosted on npm or located in a local directory is possible. These npm packages can provide custom `.mustache` files that replace default files included in the tool for the WordPress plugin or/and the block. It's also possible to override default configuration values used during the scaffolding process.
-
-### Project Template Configuration
-
-Providing the main file (`index.js` by default) for the package that returns a configuration object is mandatory. Several options allow customizing the scaffolding process.
-
-#### `pluginTemplatesPath`
-
-This optional field allows overriding file templates related to **the WordPress plugin shell**. The path points to a location with template files ending with the `.mustache` extension (nested folders are also supported). When not set, the tool uses its own set of templates.
-
-_Example:_
-
-```js
-const { join } = require( 'path' );
-
-module.exports = {
-	pluginTemplatesPath: join( __dirname, 'plugin-templates' ),
-};
-```
-
-#### `blockTemplatesPath`
-
-This optional field allows overriding file templates related to **the individual block**. The path points to a location with template files ending with the `.mustache` extension (nested folders are also supported). When not set, the tool uses its own set of templates.
-
-_Example:_
-
-```js
-const { join } = require( 'path' );
-
-module.exports = {
-	blockTemplatesPath: join( __dirname, 'block-templates' ),
-};
-```
-
-#### `assetsPath`
-
-This setting is useful when your template scaffolds a WordPress plugin that uses static assets like images or fonts, which should not be processed. It provides the path pointing to the location where assets are located. They will be copied to the `assets` subfolder in the generated plugin.
-
-_Example:_
-
-```js
-const { join } = require( 'path' );
-
-module.exports = {
-	assetsPath: join( __dirname, 'plugin-assets' ),
-};
-```
-
-#### `defaultValues`
-
-It is possible to override the default template configuration using the `defaultValues` field.
-
-_Example:_
-
-```js
-module.exports = {
-	defaultValues: {
-		slug: 'my-fantastic-block',
-		title: 'My fantastic block',
-		dashicon: 'palmtree',
-		version: '1.2.3',
-	},
-};
-```
-
-The following configurable variables are used with the template files. Template authors can change default values to use when users don't provide their data.
-
-**Project**:
-
--   `wpScripts` (default: `true`) – enables integration with the `@wordpress/scripts` package and adds common scripts to the `package.json`.
--   `wpEnv` (default: `false`) – enables integration with the `@wordpress/env` package and adds the `env` script to the `package.json`.
--   `customScripts` (default: {}) – the list of custom scripts to add to `package.json` . It also allows overriding default scripts.
--   `npmDependencies` (default: `[]`) – the list of remote npm packages to be installed in the project with [`npm install`](https://docs.npmjs.com/cli/v8/commands/npm-install) when `wpScripts` is enabled.
--   `npmDevDependencies` (default: `[]`) – the list of remote npm packages to be installed in the project with [`npm install --save-dev`](https://docs.npmjs.com/cli/v8/commands/npm-install) when `wpScripts` is enabled.
-
-**Plugin header fields** ([learn more](https://developer.wordpress.org/plugins/plugin-basics/header-requirements/)):
-
--   `pluginURI` (no default) – the home page of the plugin.
--   `version` (default: `'0.1.0'`) – the current version number of the plugin.
--   `author` (default: `'The WordPress Contributors'`) – the name of the plugin author(s).
--   `license` (default: `'GPL-2.0-or-later'`) – the short name of the plugin’s license.
--   `licenseURI` (default: `'https://www.gnu.org/licenses/gpl-2.0.html'`) – a link to the full text of the license.
--   `domainPath` (no default) – a custom domain path for the translations ([more info](https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#domain-path)).
--   `updateURI:` (no default) – a custom update URI for the plugin ([related dev note](https://make.wordpress.org/core/2021/06/29/introducing-update-uri-plugin-header-in-wordpress-5-8/)).
-
-**Block metadata** ([learn more](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/)):
-
--   `folderName` (default: `.`) – the location for the `block.json` file and other optional block files generated from block templates included in the folder set with the `blockTemplatesPath` setting.
--   `$schema` (default: `https://schemas.wp.org/trunk/block.json`) – the schema URL used for block validation.
--   `apiVersion` (default: `2`) – the block API version ([related dev note](https://make.wordpress.org/core/2020/11/18/block-api-version-2/)).
--   `slug` (no default) – the block slug used for identification in the block name.
--   `namespace` (default: `'create-block'`) – the internal namespace for the block name.
--   `title` (no default) – a display title for your block.
--   `description` (no default) – a short description for your block.
--   `dashicon` (no default) – an icon property thats makes it easier to identify a block ([available values](https://developer.wordpress.org/resource/dashicons/)).
--   `category` (default: `'widgets'`) – blocks are grouped into categories to help users browse and discover them. The categories provided by core are `text`, `media`, `design`, `widgets`, `theme`, and `embed`.
--   `attributes` (no default) – block attributes ([more details](https://developer.wordpress.org/block-editor/developers/block-api/block-attributes/)).
--   `supports` (no default) – optional block extended support features ([more details](https://developer.wordpress.org/block-editor/developers/block-api/block-supports/).
--   `editorScript` (default: `'file:./index.js'`) – an editor script definition.
--   `editorStyle` (default: `'file:./index.css'`) – an editor style definition.
--   `style` (default: `'file:./style-index.css'`) – a frontend and editor style definition.
+[Click here](https://github.com/WordPress/gutenberg/tree/HEAD/packages/create-block/docs/external-template.md) for information on External Project Templates
 
 ## Contributing to this package
 

package/lib/scaffold.js

@@ -144,7 +144,7 @@ module.exports = async (
 	success(
 		plugin
 			? `Done: WordPress plugin ${ title } bootstrapped in the ${ slug } directory.`
-			: `Done: Block "${ title }" bootstrapped in the ${ slug }directory.`
+			: `Done: Block "${ title }" bootstrapped in the ${ slug } directory.`
 	);
 
 	if ( plugin && wpScripts ) {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@wordpress/create-block",
-	"version": "4.0.0",
+	"version": "4.1.0",
 	"description": "Generates PHP, JS and CSS code for registering a block for a WordPress plugin.",
 	"author": "The WordPress Contributors",
 	"license": "GPL-2.0-or-later",
@@ -48,5 +48,5 @@
 	"publishConfig": {
 		"access": "public"
 	},
-	"gitHead": "171b87c7465b93e685e081c5f57f153507363c95"
+	"gitHead": "0d732d4b184adcb28cc83087603e81b764390d4b"
 }