Move 10up-toolkit to production dependencies; Update to latest version. #298
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.
Description of the Change
This PR closes #138 by moving the 10up-toolkit from
devDependenciestodependencies, making it available in the Node production environment.I also cleaned up some files in the block theme that don't need to be there since the root config files should take precedence.
Lastly, I updated 10up-toolkit to the latest version across the entire project.
Closes #138
How to test the Change
Make sure you can build the workspace assets in development and production environments. Run the following commands in your terminal in the wp-content directory.
export NODE_ENV=developmentnpm installnpm run buildVerify assets are built properly.
export NODE_ENV=productionnpm installnpm run buildVerify assets are built properly.
Changelog Entry
Credits
Props @claytoncollie @johnwatkins0 @Antonio-Laguna
Checklist: