Last call for @nextcloud/vue v9 breaking changes

[ShGKme]

Before releasing the final v9.0.0 and making it the main branch we should make sure that all required breaking changes are applied.

When possible, migration should be simple:

• Removed API must be marked deprecated in v8
• Changed API should have a compatible API in v8

Current breaking changes

• Vue 2 -> Vue 3
• CJS dropped
  • ✅ Forward-compatible via ESM
• dist and .js extension dropped from import path
  • ✅ Forward-compatible by just using the new paths like @nextcloud/vue/components/NcButton.
• NcSettingsSection: limitWidth prop was removed
  • ✅ Deprecated in v8
• NcAppSidebar: closing and opening events were removed
  • ✅ Forward-compatible via update:open
• v-model related changes
  • ✅ Forward-compatible via:
    • feat: forward compatibility with v9 on v-model props/events #6172
    • feat: add v-model support for input-like components #5418
• isFullscreen and isMobile are removed
  • ✅ Corresponding composables are available on both versions
• exact prop removed from VueRouter-related components
  • ✅ Comes from Vue Router migration

Proposals with breaking changes

• feat: Allow to import without dist #6385
  • ✅ Deprecated in v8 and forward-compatible
• [next] feat!: remove plugin #6349
  • ✅ Deprecated in v8 and forward-compatible
• [next] fix!: make 'box-sizing: border-box' a default behaviour for all containers #6390
  • ✅ Can be manually applied in v8, forward-compatible

[Antreesy]

IIRC there were some changes with box-sizing: border-box in next branch only (for modals and popovers)

[raimund-schluessler]

There was the idea to remove icon class support. Don't know whether this is still planned or not #3007

See #5048 as well.

[susnux]

There was the idea to remove icon class support

Yes but not now I think, there is too much old stuff that simply would break.
We also do not have agreed yet on an alternative, especially if icons are set by e.g. PHP API.
There is a discussion somewhere what to do (always inline SVG, custom icon library, etc), also a problem is we use MDI a lot but thats not where we want to go so even that is only a intermediate step.

Do we want to rename exports like Components to components or remove dist part?

Would love to see all of that, but it does not have to be breaking, we can support both without any new files (just add an alias to the exports in the package json).

Remove plugin #6349

💯

[ShGKme]

Proposal: get rid of other mixins:

• clickOutsideOptions
  • Remove
  • I haven't found usage anywhere, used internally
• userStatus
  • Remove?
  • I haven't found usage anywhere
  • Alternatively can be migrated to composable/library
• richEditor
  • Remove?
  • Used in Talk and server/apps/comments
  • Can be replaced with NcRichText