Repository navigation
chore: use the published @rtcamp and rtcamp packages, rename to rtcamp/plugin-elementary - #22
Merged
Merged
Conversation
@rtcamp/eslint-config, @rtcamp/stylelint-config and @rtcamp/wp-tooling are published, so package.json asks for ^1.1.0, ^1.1.0 and ^2.0.0 instead of the npm/* git branches, and the Tailwind feature adds @rtcamp/tailwind-config ^1.1.0. The lockfile now records registry tarballs with integrity hashes instead of git+ssh URLs. legacy-peer-deps stays, with its comment corrected: wp-tooling has no peers, but parts of the toolchain still declare older ones.
Matches the repository name. bin/scaffold.config.js keeps the placeholder identity in sync, so npm run init still replaces it with rtcamp/<slug>-features. composer.lock only gets the new content-hash.
rtcamp/wp-primitives, rtcamp/wp-phpcs and rtcamp/wp-phpstan are on Packagist, so composer.json drops their GitHub VCS repositories. The lock re-resolves them from Packagist: wp-primitives stays at v2.0.0, and wp-phpcs and wp-phpstan move to v1.0.1 (README, licence and package metadata only).
AnuragVasanwala
previously approved these changes
Oct 1, 2026
AnuragVasanwala
approved these changes
Oct 1, 2026
Merged
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.
Every package the plugin takes from rtCamp is now on a public registry, so the plugin installs them from there instead of git, and the Composer package takes the repository's name.
Changes
@rtcamp/eslint-config^1.1.0,@rtcamp/stylelint-config^1.1.0and@rtcamp/wp-tooling^2.0.0instead of thenpm/*git branches. The Tailwind feature adds@rtcamp/tailwind-config^1.1.0.package-lock.jsonchanges only those three entries, fromgit+sshURLs to registry tarballs with integrity hashes.rtcamp/wp-primitives,rtcamp/wp-phpcsandrtcamp/wp-phpstanresolve from Packagist, so the three GitHub VCS repositories are gone. wp-primitives stays at v2.0.0; wp-phpcs and wp-phpstan move to v1.0.1 (README, licence and package metadata only).rtcamp/plugin-elementaryinstead ofrtcamp/project-name-features.bin/scaffold.config.jsholds the same placeholder, sonpm run initstill producesrtcamp/<slug>-features. TheProject_Nameandproject-nameplaceholders are unchanged. The CHANGELOG and the maintenance doc say so..npmrc: the git-install note is gone.legacy-peer-depsstays, since without itnpm installfails with ERESOLVE (@babel/eslint-parserwants eslint ^9,@react-springwants react ^18); its comment now says that instead of blaming wp-tooling, which has no peers.Testing
npm ci: clean on npm 10.9 (Node 22) and npm 11.6 (Node 24)npm run lint,npm run build:prod: passcomposer validate, a cleancomposer install, PHPStan and PHPCS: passnpm run init -- --yes --name="Acme Blog" --features=tailwindon a copy: the new plugin getsrtcamp/acme-blog-features, all four@rtcamppackages on^ranges, andnpm installplusbuild:prodsucceed with@rtcamp/tailwind-configfrom npm