Replace complex webpack build process with @wordpress/scripts #62
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #61 aims to make compilations possible with an older version of node.js but I think the biggest issue with the current plugin is the complex directory layout and build process by using webpack directly.
This PR aims to replace it with
@wordpress/scripts
while also turning the plugin directory layout into a standard WordPress plugin, so it's no longer necessary to clone it to a random directory and symlinking thedist
folder (under a different name) into thewp-content/plugins
folder on the WordPress installation, you want to use it in.It also dramatically reduces the number of NPM dependencies, making future developments easier.
🚨 This is a huge breaking change though, given that the directory structure changes, so anyone using it would have to replace the symlink with the plugin directly!