Issue-126: Hoist Node Dependencies and Dev Dependencies to Root #165
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.
Summary
Fixes #126
This pull request addresses the issue of hoisting Node dependencies and devDependencies to the root of the repository when using Turbo. The goal is to ensure that after running the configure script, all dependencies and devDependencies are extracted and centralized within the root
package.json
. Additionally, workflow improvements have been made to start testing node.Changes
dependencies
,devDependencies
fromcreate-wordpress-plugin
andcreate-wordpress-theme
package.json
files.package.json
, ensuring no duplicates and maintaining alphabetical order and latest versions.alleyinteractive/action-test-general@develop
andalleyinteractive/action-test-node
for broader test coverage.How to Test
package.json
contains a comprehensive, alphabetically sorted list of dependencies and devDependencies.Additional Information
Refer to the original issue #126 for further context.