Include a11y_autocomplete_widget and JS dependency using foxy/vite method from #frontend_bundler_initiative

Closes #3472824

.ddev/homeadditions/bin/setup-repositories

@@ -11,3 +11,7 @@ for name in $(find . -maxdepth 1 -type d -name 'drupal_cms*' -printf "%P\n"); do
 done
 
 composer config repositories.drupal composer https://packages.drupal.org/8
+
+# Temporary command to fetch foxy-compatible a11y_autocomplete_element module
+# while integration under development.
+composer config repositories.drupal/a11y_autocomplete_element '{"type": "git", "url": "https://git.drupalcode.org/issue/a11y_autocomplete_element-3472705.git"}'

[Adam G-H]

Normally we'd accomplish this by patching Foxy, in drupal_cms_patches/composer.json.

[Max Pogonowski]

How would patching foxy help here? The purpose of this is to have the development branch of a11y_autocomplete_element with its composer.json/package.json files in place before the foxy plugin runs as part of composer post-install

[Max Pogonowski]

Oh.... just use a patch instead of a dev branch, right. I can try that, the foxy plugin is kinda finicky and it may not work.

[Max Pogonowski]

Yeah I tried adding the patch, but because it's in a recipe it doesn't get applied soon enough...

[Adam G-H]

Ah, I see what you mean. Yeah, if composer.json itself needs to be patched, then the only thing we could do here is have the change committed upstream before we could add this to Drupal CMS, sadly. We cannot rely on issue fork repositories because they would only apply to a local Drupal CMS development set-up, rather than "real" projects.

[Max Pogonowski]

I don't intend for this to be merged, it's here so we can see it working. Commit would definitely have to wait until the module has a compatible release