- 🇩🇪Germany Anybody Porta Westfalica
+1 for #6! Nothing to add, perfect!
So from my perspective, the bottom-up community from Vue is a super important point for Vue (and against React) but how can we find out, if it's really worth the dependency in core and if it will help us or become the next jQuery?
Perhaps this would need its own initiative or a Drupalcon workshop to find out? How should we proceed here?
- 🇺🇸United States freelock Seattle
We've done a dozen Vue projects, mostly using Drupal as a back end. I'm a big fan of Vue. But I'm struggling to see what benefit this would have getting added to core, and if it was added, how it might be used by contrib modules...
In our most recent projects, we're building Vue with our code using Vite. This creates a directory of assets that browsers load directly. We treat these apps as a complete standalone module built all at once, and bootstrapped into the browser all at once.
So if this is for a decoupled admin UI, I would think this would be built for, and within, a single admin theme, or encapsulated by a single module -- making this a module- or theme- specific library, not something directly in core.
If this were added to core, how could contrib benefit from it? What does the build process look like? What if a contrib module is depending on Vue functionality from an older, or newer, version than is in core?
- Status changed to Postponed: needs info
over 1 year ago 1:42pm 14 June 2023 - 🇬🇧United Kingdom catch
Going to move this to 'postponed, needs more info' until there's a use-case in mind. More recently project browser is using Svelte.
- Status changed to Closed: outdated
6 months ago 7:43pm 21 May 2024 - 🇺🇸United States bnjmnm Ann Arbor, MI
If we ever have to discuss again lets just open a new issue instead of looking at graying tumbleweeds.