Turbo: Drastically simplify installation for end users

Created on 14 October 2024, about 1 month ago

Problem/Motivation

Right now, installing the Turbo module requires a whole bunch of steps, including Yarn set up, Yarn patches if needed, Drupal core patches, and so on. While any serious dev should have Yarn or a similar front-end package manager, this feels like it's probably too much for the average site and will likely hinder new people wanting to try the module.

Steps to reproduce

See above.

Proposed resolution

We can probably just commit Turbo (patched) to this repository, and move the Yarn install steps to a build step for developing the module; this will remove the need for Yarn completely for sites, and also ensure that we have a known working version of Turbo that's fully patched with the patches we reference. We could implement a similar script to core's vendor-update.js which can also take care of updating our libraries entry version. Turbo itself is released under the MIT license, which shouldn't be a problem as core has multiple MIT license assets committed indicating that this should be compatible with the GPL. We just have to ensure we preserve the existing copyright.

Drupal core patches are a different story; those we could bundle with this module and have composer-patches set up in our composer.json in the short term, and work towards getting those into a stable core version in the longer term.

Remaining tasks

See above.

User interface changes

None.

API changes

None?

Data model changes

None.

📌 Task
Status

Active

Version

2.0

Component

Miscellaneous

Created by

🇨🇦Canada ambient.impact Toronto

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024