Convert build procedure to use wp-scripts

[mkaz]

• Simplifies the build procedure to use wp-scripts setup
• Removes .babelrc and webpack.config.js to use standard configs from wp-scripts
• Adjusts code to live where wp-scripts expects it to be

[mor10]

Is this the new recommend best practice for block development? If so, a lot of documentation has to be updated.

[ntwb]

LGTM 👍

[oandregal]

❤️ the simplicity of it!

[gziolo]

Is this the new recommend best practice for block development? If so, a lot of documentation has to be updated.

Documentation inside Gutenberg has been already updated. We should post in make.wordpress.org/core with more details next week. All those changes introduced should make everything easier, but it's perfectly fine to use the old workflow.

@mkaz, I noticed that each block has .gitignore file which should be either removed or updated to reflect new distribution file path.

Thanks for starting this PR. I really like how this integrates.

Finally, we can also enable linting for JS files and fix some issues like unused variables which I could quickly notice, e.g. https://github.com/WordPress/gutenberg-examples/blob/master/05-recipe-card-esnext/block.js#L1 - setLocaleData is never used.

[mkaz]

@gziolo Good catch, I missed the .gitignore. Should we exclude the built file or not?

1. The case for including, if someone downloads and runs the plugin it will work with it included. It also shows what the output should be when setup properly.

2. The case for excluding, not having it there forces the developer to learn how to build it to get it to work, it was excluded before, the file is minified javascript so versioning isn't that useful and it can easily be rebuilt when needed

I really don't have much preference.

[gziolo]

https://github.com/WordPress/gutenberg-examples#installation this says you can copy and run. I'm inclined to keep those build files and remove .gitignore files.