@Esanders, would you please add some detail? Is this for WVUI or another Vue.js project? For the former, there's some related discussion and differing perspectives in https://github.com/wikimedia/wvui/pull/76.

Can we have get an update on the WVUI and the Vector changes?

• The scaffolding needed in Vector for integration are in place on feat/search. That is, 1) Vector can consume and bundle arbitrary dependencies from NPM including WVUI, and 2) swapping out the JavaScript search implementations is done. 2 comes from WVUI and is still being developed so the swapped out implementation itself is incomplete.
• The instrumentation is not wired up yet but the plan is to use the existing SearchSuggestion in Core so changes to Vector or WVUI will likely be minimal.
• The components are not done yet but getting there. See T255902.
• IE11 support is not done yet. That's under T244287.

Are you aware of any updates as to when an initial non-rc release of Vue3 might occur?

@sbassett, no, I've not heard anything.

Sorry, but this feature is not available for testing yet as new search is not deployed to the beta cluster.

I wanted to note here that @nnikkhoui will be working on this task specifically to enable PipelineLib and CI infrastructure integration. It's been great to see strong engagement from multiple folks and read different perspectives on how to enable practical and welcoming contribution paths. This is a critical concern but there's as yet no consensus on approach as far as I can see so I kindly ask that champions for those efforts open new tickets to focus those discussions. I will be very interested to participate in them as well!

Thanks, @holger.knust and @eprodromou! @bearND, can you test out that CORS works?

@Volker_E, please review when you're back! Sorry for the pings in Slack--I forgot you were on vacation!

As far as I understand it, for the purposes of Vue.js search we will only need to pass in strings from Vector and can defer additional i18n complexity. Flipping will also be necessary and we'll take an approach similar to what @santhosh has outlined above.

Please note that the above example appears to be taken from the component snapshots which may be a special case for formatting (I think we discussed this snapshot case some, maybe in code review, but can't find the notes!).

@ovasileva, I'm working on this as part of Vue.js search so moving into the kabanana.

@ovasileva, I think(?) the Discovery-ARCHIVED folks still need to be notified. Otherwise, if the requirements identified seem correct to you, I think this task can move to sign off.

Thank you, @holger.knust!

@Anribolon, it's my understanding that you're still working on RTL support as part of this task. Is that correct or part of another task?

The code is merged but I need to update the wiki.

I don't think there's anything left to be done for this task. We have the module to load defined in T257647 and will do so on search input focus just like the old search experience. Please kick back if that's not the case.

Based on your description here, would it make sense generalize this to "publish built artifacts for production deployment" and RelEng can figure out where that would be since we're performing/organizing deploys?

Thank you, @dduvall!

Pointed as a large by Web devs asynchronously.

Pointed as a large by Web devs asynchronously.