goal: level of effort (approx.)
Suggestions:
- Use v8js for SSR
- Let PHP do the templating and use Vue.js in script tag, without .vue files
Timebox: 1 day (8 working hours) per approach
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T394621 [MEX] Mobile Editing Experience of Items Project | |||
| Resolved | karapayneWMDE | T394886 [MEX] M2 - Iteration 2 - Basic UI elements | |||
| Resolved | karapayneWMDE | T398031 [MEX] Create ADR for SSR | |||
| Resolved | karapayneWMDE | T397291 [MEX] M2 - Spike - Alts to php-vuejs-template |
Event Timeline
Comment Actions
V8JS
- Current docker images of mediawiki don't have required binaries to install V8JS for PHP 8.1, therefore it's needed to update python and ninja versions to install it in the first place.
- Having required binaries doesn't make it easy to install, it has a lot of dependencies and this arises security issues as @hoo mentioned before in a call.
- Even after several attempts I wasn't able to run it smoothly with current .vue files we have
- It needs a lot of boilerplate code and it's easier to use node which has v8 as well, it can be replace with node
- After spending more than a day, I decided not to continue with V8JS
Comment Actions
Hydrating PHP Template with VueJS
- The plan was to create the HTML via PHP and hydrate it with VueJS
- I have tried to use our existing templating classes but couldn't make it happen
- There is too much steps to make it happen and it leads to have a lot of boilerplate code like V8JS
- Then I've investigated current mechanism and I figured out that it needs as much effort as using current php-vuejs-templating approach and this eliminates the intended "less development effort" aim unfortunately.
- With this approach, it's impossible to use codex Vue components, which is another downside
Finally, I think it seems like both of the above approaches doesn't have any significant advantage compared to php-vuejs-templating