Consider moving from Parcel to Webpack about cliff-wp-plugin-boilerplate HOT 4 CLOSED

After playing with this a long while, the answer is 'no'... because:

• Parcel was working, including HMR, and is only going to improve overall with Parcel 2.
• Extending @wordpress/scripts' webpack was more setup code than Parcel's (added complexity) and didn't give us any benefits.
• wp/scripts' webpack says it's subject to change (which could be beneficial if we're just inheriting), but the granular integration steps makes our code more brittle.
• wp/scripts only packages JS files, not JSX, PCSS, SASS, or even CSS files -- for concatenation, minification, etc.
• We can use wp/scripts' scripts (e.g. linting and checking licenses) if we want to without needing to extend their webpack.
• WP + React + webpack just isn't giving us HMR without having to define the URI we're running on (lame) or wrap our code with things like hot() or import extra <script> in the entry file's header
• Each of our glob-added PostCSS files had an empty or near-empty style.pcss.json file generated alongside them, which is cruft. (Unsure which package/command was causing this, but it definitely seemed intentional.)

For reference, we gave it the full effort: https://github.com/cliffordp/cliff-wp-plugin-boilerplate/pull/80/files

from cliff-wp-plugin-boilerplate.

I came across this, thanks for sharing! I've been assessing different building tools/setups for creating Gutenberg blocks.

from cliff-wp-plugin-boilerplate.

Hi, @skorasaurus

Glad you found this. Let me know if there's anything I can do to help.

from cliff-wp-plugin-boilerplate.

A neat little enqueue trick I found along the way, if using WP's webpack: WordPress/gutenberg#18471 (comment)

from cliff-wp-plugin-boilerplate.