Managed-site update script fails to load when an optional toolchain module is absent

Internal Proven Solved Case solved case

Proven in the project context it was captured from. It is not universal Drupal truth and widening it requires review.

The managed-site update entry point aborted before performing any work when it was executed from a reconstructed toolchain that did not ship one of its imported modules.

Record case.drupal.solved.code-change.5bffad1b0b45288d

What this is

What is this
solved case: Managed-site update script fails to load when an optional toolchain module is absent
Why it exists
A real problem was solved and verified in one observed project context.
What makes it authoritative
Proven in the project context it was captured from. It is not universal Drupal truth and widening it requires review.
Project scope
This record is scoped to the context it names and is not a Drupal-wide rule.
Recommended next step
Treat it as a worked example for the context it names, not as a rule.
Was anything changed
No. Querying Drupal Knowledge changes nothing.

What is not known

  • Proven in one observed project context. It is not universal Drupal truth.

What the record states

Values as recorded. Blank means the record did not state one.
Claimed scopeproven_context_only
ConditionsApplies to Node ESM entry points executed from a reconstructed partial toolchain
Drupal versions11.4.5
Widening it requires reviewyes
LimitationsProven on a single project and a single Drupal core version, Verified through the repository test suite only, not under production load, Describes a tooling defect, not a Drupal core or contrib defect, Carries no security severity evidence
Projects it has been proven on1
Php versions8.3
ProblemThe managed-site update entry point aborted before performing any work when it was executed from a reconstructed toolchain that did not ship one of its imported modules.
Project identity disclosedno
Root causeA static top-level ESM import created a hard load-time dependency on a module that the reconstructed toolchain deliberately does not copy, so module resolution failed before the entry point executed.
Root cause stateconfirmed
SolutionReplace the static import with a call-time dynamic import so the entry point stays loadable., Declare the module directory as part of the toolchain the reconstruction copies.
Statusverified
SymptomsNode exited with ERR_MODULE_NOT_FOUND before any update logic ran, No machine-readable result document was produced, The failure occurred identically on every invocation, including dry-run
Verificationautomated_test: passed (release pipeline phase 3 suite), reproduction_before_and_after: passed (validate-pack exit code transition 1 -> 0)

Provenance

This record's authority is internal to Drupal Knowledge; no external source snapshot stands behind it.

  • internal_solved_case · case.drupal.solved.code-change.5bffad1b0b45288d