WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@claytoncollie
Copy link
Contributor

Description of the Change

This PR closes #138 by moving the 10up-toolkit from devDependencies to dependencies, 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.

  1. export NODE_ENV=development

  2. npm install

  3. npm run build

  4. Verify assets are built properly.

  5. export NODE_ENV=production

  6. npm install

  7. npm run build

  8. Verify assets are built properly.

Changelog Entry

Changed - moved 10up-toolkit to the list of dependencies. Updated to version 6.5.0

Credits

Props @claytoncollie @johnwatkins0 @Antonio-Laguna

Checklist:

Copy link
Member

@fabiankaegy fabiankaegy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense :) Thanks for the fix!

@fabiankaegy fabiankaegy merged commit be82de5 into trunk Jul 17, 2025
8 checks passed
@fabiankaegy fabiankaegy deleted the feature/138-dev-dep-clayton branch July 17, 2025 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include 10up-toolkit in NPM dependencies instead of devDependencies

2 participants