Nuxt 3

[surchs]

Starting to collect some information and resources here as we find / discuss them, so we can refer to them later.

Nuxt3 is a breaking change, but the main barrier are likely going to be the 3rd party libraries we use.
See the official statement on the upgrading decision: https://v2.nuxt.com/lts/

Aside from that, the big new thing in Vue3/Nuxt3 is composition API: https://vuejs.org/guide/extras/composition-api-faq.html

3rd party stuff

• Component library.
  • Right now we use
    • https://bootstrap-vue.org/. 🛑 There is "initial" Vue3 support (https://bootstrap-vue.org/vue3) but activity has been (understandably) sparse (core dev is Ukrainian), unlikely to catch up
    • https://vue-select.org/. ✔️ seems to work: https://vue-select.org/guide/components.html#vue-3x
  • What are replacements
    • https://primevue.org/. Very extensive library, great data table, active maintenance, company behind
    • https://element-plus.org/en-US/. extensive library, great data table, active
    • https://www.naiveui.com/en-US/os-theme. good library, meant to be custom styled, active, probably bit less "batteries included"
    • several of the "big" component libraries have not caught up / stumbled the transition. e.g. vuetify still only has experimental data table support
• Testing
  • Right now we use
    • https://www.cypress.io/. 🟨 e2e tests (should) work as before. Component tests are not supported (and even Nuxt2 support is still in alpha) https://docs.cypress.io/guides/component-testing/vue/overview#Nuxt. There is Vue3 support, but progress towards Nuxt 3 component tests seems slow so I would not count on that happening and even then be likely buggy for a while. As Cypress is just a big wrapper of testing libraries, unit tests might also work.
  • What are replacements
    • Unit tests: vue-test-utils directly. Unit tests only affect store functions. The Vue3/Nuxt3 store is pinia and it comes with nice docs on how to test the store https://pinia.vuejs.org/cookbook/testing.html
    • Component tests: https://storybook.js.org/. This will likely be the biggest difference in workflow - and the most "bleeding edge" nuxt3 support. Storybook is a very widely used tool exclusively for component testing. It's pretty GUI oriented / easy to use, but has automatic test runners for CI. The biggest challenge is getting it to work with Nuxt3 as this is still very early days, however very actively being developed: https://github.com/storybook-vue/storybook-nuxt
    • e2e tests: https://playwright.dev/. We can obviously stay with cypress here, as e2e still works. But the main benefit for cypress is the everything-from-one-library aspect. If we don't use it for unit and component tests, then I think playwright has the better DX for e2e (see e.g. https://www.youtube.com/watch?v=Wgp1a1XRq3I), and they have early-days component tests: https://playwright.dev/docs/test-components - unclear if nuxt works, next.js does ...

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!

[surchs]

We will most likely not move to Nuxt3 so I am closing this