feat: cheap Vue 3 support via separating core login and ui by package exports

[ShGKme]

Resolves

• Intermediate solution for [RFC] export of vue components #1809
• Currently @nextcloud/uploads has uploading logic and ui mixed
• Also, it has some circular dependencies
• This PR includes:
  • Refactoring modules structure:
    • core - pure uploading logic
    • ui - UI related functions (dialogs) that use Vue only internally
    • components - exported Vue component (that can only be used in a specific Vue version)
  • Providing core, components and ui as npm package exports
  • Defining vue and @nextcloud/vue as direct dependencies to allow installation in Vue 3 environment

// Works in both Vue 2 and Vue 3 (doesn't rely on Vue at all)
import { getUploader } from '@nextcloud/upload/core'

// Only works in Vue 2 (only in Vue 3 after migration)
import { UploadPicker } from '@nextcloud/upload/ui'

// Old import still works
// But also only in Vue 2
import { getUploader, UploadPicker } from '@nextcloud/upload'

Detailed explanation

Details

[Antreesy]

Tested against Talk / Vue 3

[susnux]

As this is a breaking change, its still the question if we want to keep this package to depend on vue in general.
Or just move the dialog to the dialogs package and the Uploader to the vue package to keep it API only.

I would prefer that, but this is also a nice solution :)

[ShGKme]

As this is a breaking change

There are no breaking changes. There is still the root export with everything.

[ShGKme]

This PR is feat.

It adds 2 new exports:

1. @nextcloud/upload/core with uploading related logic and functions
2. @nextcloud/upload/ui with Vue components and dialogs

The existing @nextcloud/upload with index.ts stays in place

[ShGKme]

@susnux Please, have a look at the last image in the PR : )

[susnux]

There are no breaking changes. There is still the root export with everything.

But then I still do not see how this solves the problem aslong as this exports a vue component its not universal.
Meaning we still need two version for vue 3 and vue 2.

Then we also could just migrate the library as is?

[Antreesy]

Then we also could just migrate the library as is?

If time allows, that would be nice.
Otherwise we can unlock apps, that do not use Vue components, with a minor release, and invest more efforts, then it will be actually required

[ShGKme]

But then I still do not see how this solves the problem aslong as this exports a vue component its not universal.

This library has Vue component UploadPicker and many functions, including pure JS functions with uploading logic.

This UploadPicker is the only part that actually depends on Vue version.

But when everything is exported together from a single index.ts, you cannot use even getUploader with a different vue version. Because Vue is also imported.

This changes separates these parts.

It allows importing getUploader without importing Vue, and use it in any app (both Vue 2 and Vue 3).

If we continue as shown on the new image, then all the other functions can also be used with shipped Vue.

[ShGKme]

Meaning we still need two version for vue 3 and vue 2.

Only for a one thing - UploadPicker

[ShGKme]

Then we also could just migrate the library as is?

Yes, but it is independent.

And you still need to use library in Vue 2 apps.

[ShGKme]

I can also separate this PR to pure refactoring (I believe it helps to separate the library anyway + removes cycles) and to adding exports (to make the library 2/3 Vue 3 compatible).

@susnux @skjnldsv What do you think?

This is the last library to make Nextcloud ecosystem Vue 3 ready 👀

[ShGKme]

• Closing in flavor of refactor: split vue and dialogs sub modules to prepare for library splitting #1816