[horde] Javascript / Frontend refactoring: Tester wanted

[Nels Lindquist]

On 2026-04-23 1:05 PM, Mike wrote:
 >
 > Quoting Ralf Lang <ralf.lang at gmail.com>:
 >
 >> I am looking for a brave soul who is willing to apply three big
 >> patches to
 >> their Horde javascript
> 
> I'm looking into doing this, however, I don't want to dork up my current 
> testing configuration.
> 
> I thought I'd approach this by:
> 
>   - creating a new web dir location and cloning bundle into it
>   - add imp, kronolith, and turba as a minimum
>   - create separate directories for the individual repos of imp, 
> kronolith, turba
>   - modify the composer.json to use "path" entries to use these repos
>   - update those repos with the prospective PR's mentioned below
>   - update my web configuration as needed.
> 
> Am I making this harder than it needs to be?

You might be? First--maybe wait for Ralf to chime in--I had the 
impression he'd moved on from the testing phase with those JS updates 
and at least some of what was learned has been incorporated into the 
main development branch already.

Second, you could just use composer to apply those versions to your 
testing environment, and then revert back just as easily.

To apply:

composer require horde/imp:dev-refactor/vanilla-js-migration
composer require horde/kronolith:dev-refactor/vanilla-js-migration
composer require "horde/horde:dev-refactor/vanilla-js-migration as 
6.0.0beta14.1" (*)

To revert:

composer require horde/imp:*
composer require horde/kronolith:*
composer require horde/horde:* -W

You might want to restart php-fpm (if relevant) and clear your Horde css 
cache after each switch.

(*) I needed the alias to get past core interdependencies in other 
installed modules. At the time, horde/horde 6.0.0beta14 was the 
"released" branch; today it's horde/horde/6.0.0beta15. YMMV.


-- 
Nels Lindquist
nlindq at maei.ca