Repository navigation
chore(init): remove the Dev Tools feature for now - #37
Merged
Merged
Conversation
Drop bin/features/dev-tools.js, its tests, the end-to-end script and its docs, its entry in bin/scaffold.config.js, and the mentions in AGENTS.md, the init skill and prompt, and the docs. rtcamp/wp-dev-tools is not public yet, so the toggle only worked with repository access.
AnuragVasanwala
previously approved these changes
Oct 1, 2026
Its only target was tests/js/scaffold-config.test.js, removed with the Dev Tools feature.
AnuragVasanwala
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Removes the optional Dev Tools feature from
npm run initfor now. It wiredrtcamp/wp-dev-tools, which is not public yet, so enabling it only worked with access to that repository.Changes
bin/features/dev-tools.js, its entry inbin/scaffold.config.js, its tests (tests/js/scaffold-config.test.js), the end-to-end script (bin/dev-tools-e2e.sh) and its docs (docs/dev-tools-demo.md,docs/internal/dev-tools-e2e.md).AGENTS.md, the/initskill, the Copilot init prompt and the docs.tests/js/scaffold-config.test.js. Its mentions indocs/initialization.mdanddocs/internal/maintenance.mdare removed too..wp-env.override.jsonstays in.gitignore, since it is a regular wp-env file.graphify-out/baseline is unchanged; it is rebuilt by maintainers.tests/js/scaffold-config.test.jsonly covered Dev Tools, so the skeleton now has no Jest tests.test:jsalready runs with--passWithNoTests.Testing
npm run init -- --listshows only Tailwind and HMR;--enable=dev-toolsnow fails withUnknown feature key(s): dev-tools. Valid keys: hmr, tailwindnpm run init -- --name="Acme Content" --version=1.0.0 --yes --keep-exampleson a copy: passes, withCleanup (skipped)npm run lint:js: passes