Remove Custom Webpack Configs

[douglas-johnson]

Related Issues

• Resolves Remove custom webpack configs since wp-polyfill is no longer included by default #15

What Was Accomplished

• Removed custom webpack configuations from Newsletter and Table of Contents blocks.
  • Those configs existed to prevent the wp-polyfill from being included as a dependency. Now that is the default behavior.
• Updated the package.json to remove reference to those configurations.
• Built both blocks using the updated configuration.
  • Only newsletter changed, even then it was only the version number. The distributable block files are identical, there's just fewer config files.

A note on @wordpres/scripts

I had to update my global install of @wordpres/scripts to get this to work. One of their dependencies was having a problem with a failing post-install script.

To get it working, I had to:

• Update to the latest version of Node through NVM
• run export NODE_OPTIONS=--openssl-legacy-provider to support Node 17.
• Install @wordpress/scripts globally with the --ignore-scripts setting

[richdacuban]

@douglas-johnson Looks good to me, after I got npm udated to 17 and wp-scripts updated to latest I was able to build to run the two npm commands to build the newsletter and table of contents blocks.

Checking them out in Cata via Local, the newsletter block needed to be recovered but it was successful. The table of contents block had no recovery needed and was fine.