Problem/Motivation

Counting that we already use YARN/NPM to compile SCSS into CSS it make more sense to use them to manage Bootstrap library than Composer.

Proposed resolution

  • Add Bootstrap library to package.json dependencies of sub-themes
  • Update documentation

Remaining tasks

  • Merge request
  • Review
  • Merge

Issue fork ui_suite_bootstrap-3586139

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

rosk0 created an issue. See original summary.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented

Hi,

Thanks for your proposal.

If you use Node package managers to install the Bootstrap library in your sub-theme, I suppose the library will be in a node_modules folder inside the sub-theme and not in the Drupal "libraries" folder?

Then in this case you can POC another starterkit if you want, but it may also impact the base theme too? In this case, I don't think this will get merged.

rosk0 opened merge request !324

rosk0’s picture

rosk0
he/him
Primary language Russian
Location Wellington
commented
Assigned: rosk0 » Unassigned
Status: Active » Needs review

Please have a look. T

I don't see a point in another sub-theme as it has no distinctive properties to stand out from existing themes.

The idea is simple, if you use of the the sub-themes, you use NPM or YARN to manage dependencies, not Composer. Base theme expectations of the Javascript location are corrected using library override.

The docs need to be updated and maybe some edge case missed , but overall this works.

Love to hear your feedback.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Assigned: Unassigned » grimreaper
Issue tags: +DevDaysAthens2026
grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Assigned: grimreaper » Unassigned
Status: Needs review » Postponed

Hi,

Thanks for the MR.

I prefer Composer to also handle external libraries because (with assets packagist) it is easy to check for new versions when checking also Drupal core and contrib updates.

I currently don't want such changes in the starterkits.

But I am ok to document it.

Keeping the issue opened to see if this gains some feedbacks from other people.