docs: #3620356 Correct the CI comment that described the removed drupal-libraries yarn sync

Rajab Natshahrequested to merge
issue/varbase_news_base-3620356:3620356-libraries-via-composer into 1.0.x

Issue: https://www.drupal.org/project/varbase_news_base/issues/3620356

What and why

Varbase 11 used to get six front-end libraries by running scripts/drupal-libraries-sync.js, a Node script that copied files out of node_modules/ into web/libraries/, driven by a drupal-libraries block plus six npm dependencies and a postinstall hook in package.json. That is replaced by Composer packages on Packagist, each required by the module or the varbase_* recipe that actually loads it: vardot/aos 2.3.4, vardot/jquery.fancytree 2.38.5, vardot/ckeditor5-media-embed-drupal 47.6.2, vardot/ace 1.44.0 and vardot/dropzone 5.9.3 (all type: drupal-library, all on Packagist), plus swagger-api/swagger-ui, which drupal/openapi_ui_swagger already required and which only needed an installer path.

Comment-only change to .gitlab-ci.yml. The comment said --no-scripts skips the varbase drupal-libraries yarn sync (ace, dropzone, …). There is no such sync any more, so the comment described something that no longer exists.

The corrected comment says what --no-scripts actually skips now (the project's own composer scripts) and adds a fact worth stating explicitly: the front-end libraries are placed by composer/installers installer paths, which are plugin-driven rather than scripts, so --no-scripts does not stop web/libraries being populated.

No job, command or flag changes.

Verified on a freshly installed Varbase 11.4.5 site in DDEV with the packages resolved from Packagist and no VCS repositories: 14/14 declared library files present, 10/10 assets HTTP 200, 7/7 Drupal libraries discovered with every asset resolving, status report green, and yarn install succeeds with none of the six npm library packages present.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports