Move to vite for bundling

[juliushaertl]

• Introduce vite for building
• Bump @nextcloud/vue
• Bump @nextcloud/dialogs and @nextcloud/files
• Adjust code to changes in libraries
• Drop 26 suppport as there is no support for javascript modules that are required by vite chore: Drop Nextcloud 26 for the next release as it is EOL #1179

[enjeck]

@juliushaertl You say "based on #647", but I don't see how?

[juliushaertl]

I based my branch locally on top of yours and then created a pull request towards that one. You can also sett that in the github ui:

Once your PR/branch gets merged github automatically changes this, but that way I can make use of your changes already during development.

[enjeck]

Doesn't work for me after running npm ci and then npm run dev. Am I missing something?

[juliushaertl]

Sorry, it isn't ready yet, didn't wanted to ask for review but the ones got autoassigned by github 🙈 I'll ping you once I'm ready :)

[max-nextcloud]

Looks great! Thanks for looking into this.

I have some minor comments only.

Locally I get a warming when building:

I think the ?? '' can just be removed in this case - but it would also be nice to catch such warnings in the ci or so. However i was not able to trigger that check on its own.

I also noticed that tables have dark favicons for me now:

I don't know if that's related. Will try and build with main branch to compare.

[max-nextcloud]

I also noticed that tables have dark favicons for me now:

Just tried with current main with the same result. So not related to this PR.

[juliushaertl]

Likely caused by #712 then

[juliushaertl]

We need to decide when to merge this, currently the vite build requires nextcloud/server#36057 which is 27 only.

[juliushaertl]

@susnux I'm having some trouble here with the npm run watch command which always exits after the first build. Is that something you've seen already? Any clue why that might happen? We just call vite --mode development build --watch

[susnux]

@susnux I'm having some trouble here with the npm run watch command which always exits after the first build.

Should be fixed now: vitejs/vite#15951

[susnux]

I think the ?? '' can just be removed in this case - but it would also be nice to catch such warnings in the ci or so. However i was not able to trigger that check on its own.

The warning means that the right part is never null / undefined because 'string' + variable ?? 'fallback' reads as:

1. 'string' + variable
2. ?? Then check the result is null or undefined
3. Then fallback to 'fallback'.

So just brackets are missing like 'string' + (variable ?? 'fallback').

(Otherwise you might get 'stringnull' as the result)

[juliushaertl]

@susnux The two issues i mentioned in person now on this PR after updating @nextcloud/dialogs

• The file picker dialog loading fails (a quick patch for the dialogs library is below but I'm unsure if that is the proper approach)
• Once that is patched the dialog does not return any selected file

diff --git a/lib/composables/isPublic.ts b/lib/composables/isPublic.ts
index ec89e8b..a1000ca 100644
--- a/lib/composables/isPublic.ts
+++ b/lib/composables/isPublic.ts
@@ -10,7 +10,7 @@ import { onBeforeMount, ref } from "vue"
 export const useIsPublic = () => {
        const checkIsPublic = () => (document.getElementById('isPublic') as HTMLInputElement|null)?.value === '1'

-       const isPublic = ref(true)
+       const isPublic = ref(checkIsPublic())
        onBeforeMount(() => { isPublic.value = checkIsPublic() })

        return {