Search by

loopress / php-attributes

jean-smaug

PHP attribute classes referenced by Loopress api/ route files and hooks/ files, for editor autocomplete and static analysis. Declarations only, nothing executes.

Package info

github.com/loopress/loopress

Homepage

Language:TypeScript

pkg:composer/loopress/php-attributes

Security

Advisories: 0

Aikido package health analysis

Transparency log

Statistics

Installs: 1

Dependents: 0

Suggesters: 0

Stars: 1

Open Issues: 5

dev-main 2026-09-11 15:42 UTC

Requires

  • php: >=8.2

Requires (Dev)

None

Suggests

None

Provides

None

Conflicts

None

Replaces

None

GPL-2.0-or-later e614f477a04ee184176dccc4fe2d7061828843b0

wordpressattributesstatic-analysisloopress

Published on Packagist.org on 2026-09-11 15:42 UTC

This package is auto-updated.

Last update: 2026-09-11 15:43:16 UTC

README

Make WordPress reproducible: sync ACF field groups, SEO settings, code snippets, Composer dependencies, pages, forms, and custom REST routes between WordPress and a Git repository, driven by a single CLI. Configuration as code, version control, reproducible environments, instead of clicking through wp-admin and hoping staging matches production.

loopress.dev · Documentation · Security policy

What's in this repo

This is the loopress/loopress pnpm workspace: the CLI, the companion WordPress plugin, the marketing site, and the docs all live and version together here.

Package What it is
cli/ @loopress/cli, the lps command. Talks to the WordPress plugin's REST API to pull/push everything.
mcp/ @loopress/mcp, the lps-mcp MCP server. Exposes CLI operations as tool calls for AI agents.
wordpress-plugin/ The WordPress plugin (loopress) the CLI talks to. Ships as two editions, Light (wordpress.org) and Full (loopress.dev only), from one codebase.
website/ The loopress.dev marketing site (Astro + React).
documentation/ The docs site (Astro + Starlight) at docs.loopress.dev.
e2e/ Playwright tests running the real built CLI against a real, disposable WordPress instance.
assets/ Shared brand assets (@loopress/assets: logo, icons) consumed by the plugin and the website.
eslint-config/ Shared ESLint config (@loopress/eslint-config) for the JS/TS packages.

Each package has its own README with the details, this one is just the map.

Requirements

  • Node 24.x
  • pnpm (version pinned in package.json's packageManager, run via corepack enable or install it directly)
  • PHP + Composer for wordpress-plugin/ (see its own README)

Getting started

pnpm install   # installs the whole workspace from the repo root

Then jump into whichever package you're working on:

cd cli && pnpm dev                # CLI, watch mode
cd wordpress-plugin && composer install && pnpm dev:full   # plugin admin UI, watch mode
cd website && pnpm dev            # marketing site
cd documentation && pnpm dev      # docs site

Testing

  • Unit tests: run inside each package (pnpm test in cli/, composer test in wordpress-plugin/). No network, no WordPress instance needed.
  • E2E tests (e2e/): the real CLI against a real, disposable WordPress instance. See e2e/README.md for how to point them at one, locally or via the same Docker stack CI uses.

Links

Both are rebuilt on every push to main (see .github/workflows/mutation-report.yml) and published to GitHub Pages. Report-only for now, not a merge gate, the plugin job runs with continue-on-error: true (see wordpress-plugin/infection.json5).

Releasing

Versioning and changelogs are managed with Changesets. Run pnpm changeset when a PR changes published package behavior, and describe it as a patch, minor, or major bump for whichever package(s) it touches.

License

MPL-2.0