Migration from CGB to @wordpress/scripts

[jrtashjian]

This has been a bit more difficult than anticipated specifically around our styles and code splitting with webpack 4. There is still some cleanup to do around dependencies and scripts but this is now compiling our JS and CSS using @wordpress/scripts and postcss with node-sass.

I've gone through multiple iterations of trying to simplify our styles compilation here and I think this is the best solution without too much of an overhaul. PostCSS and Sass don't really seem to work well together when it comes to compiling and from what I've seen and read it seems migrating to PostCSS could be a benefit for us.

Tasks:

• Remove unused dependencies
• Remove unused npm scripts
• Remove unused grunt scripts
• Ensure Jest tests run with wp-scripts test:unit
• Remove SCRIPT_DEBUG usage to resolve ISBAT use SCRIPT_DEBUG mode with CoBlocks #1160

[AnthonyLedesma]

Tested and things are working on my end. Was able to get up and running very easily.

[ramonjd]

Hi @jrtashjian, I hope this isn't a dumb question: what does "CGB" stand for?

😸

[jrtashjian]

@ramonjd Not at all! "CGB" stands for Create-Guten-Block. It is a tool that is used to scaffold out a plugin for developing blocks. It hadn't been updated in a while and wp-scripts is a similar tool (maintained by the Gutenberg project). This PR was to transition into the new tool :)

Here's the CGB project on GitHub if you're curious:
https://github.com/ahmadawais/create-guten-block

[ramonjd]

"CGB" stands for Create-Guten-Block.

Thanks for the quick response. We were betting on something like Chips Gravy Bun, but Create-Guten-Block is also fine. :)