Repository navigation
docs: refresh setup notes and link wp-primitives v2.0.0 - #40
Merged
Merged
Conversation
- Link the wp-primitives v2.0.0 docs; composer.json requires ^2.0. - Dependencies come from Packagist and npm, not GitHub. - npm install adds a pre-commit hook as well as the commit-message hook. - wp-env activates the plugin itself; the tests use .wp-env.tests.json. - An initialized plugin has no Jest tests until one is added. - .nvmrc 22.22.2 and engines.node match @wordpress/scripts 36.
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
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.
Doc and setup fixes from a fresh-clone test of the skeleton.
Changes
composer.jsonrequires^2.0. They now point at v2.0.0; every linked file and anchor exists there. The dated validation record indocs/internal/maintenance.mdkeepsv1.0.1.docs/getting-started.mdsaid the packages come from GitHub. They come from Packagist and npm.npm installinstalls a pre-commit hook that runs lint-staged as well as the commit-message hook; both guides say so.wp-envactivates the plugin when it starts, so the documented activate command printed "Plugin is already active". Both guides now say when the command is needed.docs/getting-started.mdsaid.wp-env.jsonmounts the plugin in the test site too; the tests use.wp-env.tests.json.npm run test:jsreports none;docs/local-development.mdsays so..nvmrcis22.22.2, andengines.nodeis^22.22.2 || ^24.15.0 || >=26.0.0, the range@wordpress/scripts36 requires.npm installon Node 22.20 printed 5EBADENGINEwarnings.Testing
npm run lint:package-jsonand Prettier onpackage.json: pass