...

• npm ci to make sure you have the correct version of all of the packages

• Run eslint (npm run tui-style-check), fix the issues.

• Build tui, fix any issues the compiler complains about.

• Test everything works in the browser, while keeping the console open to see any runtime warnings.

Testing

Test the Tui/Vue front-end of the features/code you have built. Test that everything looks and works okay, and that there aren’t any errors or warnings in the browser console.

Try all possible states and interfaces – especially interactive things and things that make GraphQL requests.

Breaking changes

You can see the full list of breaking changes in the Vue documentation, but some of the most impactful are summarised below.

It may also be useful to familiarise yourself with the Vue 3 documentation.

It is also safe to assume that any core component overrides will need to be checked and updated to Vue 3. Changes to core components' public API are documented in upgrade.txt.

We don’t recommend attempting to replace vue with the the @vue/compat build -- in our experience, the compatibility layer is not reliable, and many options will need to be disabled as our codebase has been migrated to Vue 3 already.

Event handling (eslinted)

...

The .native modifier no longer exists, instead when attaching a listener (e.g. @click="..."), any event listener that is not declared in the emits field of the component will now also be attached as a native event handler listener to the root element of the component.

...