README

Drupal base (contrib, core and wxt version) for a great wxt based project, all the contrib modules and core recipe (patches) that have been curated for high performing very functional wxt based projects. Intended to be used as a composer require.

fork protox as a baseline to start with

https://gitlab.com/agrcms/protox

dxbase

Drupal base (contrib, core and wxt version) for a great wxt based project, all the contrib modules and core recipe (patches) that have been curated for high performing very functional wxt based projects. Intended to be used as a composer require.

fork protox as a baseline to start with

https://gitlab.com/agrcms/protox

📦 Managing drupal/linkchecker via agrcmsx/dxbase

This guide outlines how to manage the inclusion or removal of the drupal/linkchecker module using the agrcms/dxbase Drupal distribution. It is written in the context of issue #3525930.

🔍 Overview

• agrcmsx/dxbase is a base build that defines common module dependencies.
• Projects like proto or protox consume dxbase as a Composer dependency.
• drupal/linkchecker is currently managed within agrcmx/dxbase/composer.json and propagates downstream through standard Composer resolution.

📌 Current Inclusion

The module is explicitly required in dxbase:

composer.json in dxbase – line 394:

"drupal/linkchecker": "^2.1@alpha"

➖ Removing linkchecker

If you no longer want drupal/linkchecker to be pulled into downstream projects:

Step 1: Remove from dxbase

Delete the relevant line in agrcmsx/dxbase/composer.json:

- "drupal/linkchecker": "^2.1@alpha"

Step 2: Tag a New Release

Create a new Git tag for the updated agrcmsx/dxbase project:

git tag 11.1.3.6
git push origin 11.1.3.6

Replace 11.1.3.6 with the appropriate next tag version.

Step 3: Update the Downstream Project

In proto, protox, or any consumer of dxbase, update the dependency and re-run Composer:

composer update agrcmsx/dxbase drupal/linkchecker

Confirm that drupal/linkchecker has been removed from:

• composer.lock
• /vendor
• Drupal's core.extension configuration (if previously installed).

✅ Notes

• If a downstream project still needs drupal/linkchecker, it can explicitly require it locally:

composer require drupal/linkchecker

• This workflow is a standard Composer practice, but due to centralized dependency control in dxbase, changes must begin upstream.

🔗 Related

• Linkchecker issue #3525930
• agrcms/dxbase GitLab repo

🩹 Updating Patches for drupal/linkchecker

agrcmsx/dxbase uses the cweagans/composer-patches plugin to manage patches applied to Drupal core and contrib modules, including drupal/linkchecker.

You can view the current patches for drupal/linkchecker in composer.json under the extra.patches section:

"drupal/linkchecker": {
  "3522806 - Check for null parent_entity_type_id":
    "https://www.drupal.org/files/issues/2025-05-05/3522806-04.patch",
  "3426268 - Check on demand":
    "https://www.drupal.org/files/issues/2025-05-05/3426268-13_0.patch",
  "Linkchecker interval , 2 minute interval for debugging purposes":
    "https://www.drupal.org/files/issues/2021-05-07/linkchecker-interval_for_debugging-3212816-3.patch",
  "321320 - Allow linkchecker in a non-standard environment, host and port substitution without skip published option.":
    "https://www.drupal.org/files/issues/2024-12-30/3213210-40.patch",
  "3525930 - Do not linkcheck anything that isn't in the published moderation state":
    "https://www.drupal.org/files/issues/2025-05-22/3525930-01.patch"
}

🔄 How to Update a Patch

To update an existing patch or apply a new one:

1. Find or create the new patch on drupal.org or locally.
2. Replace or add the entry under the extra.patches.drupal/linkchecker section in composer.json with the new patch URL or file path.

3. Rebuild the Composer lock file:

   composer update drupal/linkchecker --lock
   

4. Confirm the patch is applied:

   composer show -p drupal/linkchecker
   

   You can also inspect vendor/composer/installed.json or verify the patch was logged during install.

5. Tag a new dxbase release so that downstream projects can consume the patch:

   git tag 11.1.x.y
   git push origin 11.1.x.y
   

6. Update the consuming project (e.g., proto, protox):

   composer update agrcmsx/dxbase drupal/linkchecker
   

✅ Notes

• Patch entries can include comments as keys; use meaningful descriptions with issue numbers for clarity.
• You can also use local patch files (e.g., patches/fix-linkchecker-crash.patch) instead of remote URLs.
• Ensure that changes to patches do not conflict with future module updates or existing patches.