-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple assets loading #2451
Comments
Isn't there a vendor.js that ships most of the dependencies such as Vue, Vuex, ...? |
Yep, most parts should be shared from the vendors or editor-*.js files as the size of the bundles indicate:
But we can of course have a look if splitting like that still makes sense. The main reasoning behind the split and dynamic imports was that with the viewer we can only load the heavy parts if the user is actually opening the text app, e.g. on talk or the dashboard. The text-public.js entrypoint we may drop once viewer is used on public pages of single shared files: nextcloud/viewer#508 |
A bit off topic: Maybe ModuleFederation of vendor packages ( Even without any additional applications installed that would reduce the traffic of JS files about 10% (as currently |
It is in my personal roadmap @susnux |
Are we still interesting in picking this up, at some point? It's been roughly a year since. |
Now is created one bundle for each "viewer" / "page".
main.js
files.js
public.js
viewer.js
Each of these files is bundled with Vue, Vuex, Nextcloud Components, Tiptap, CSS...
Although, the main issue could be the page load, it is causing other issues like "CSS collisions" and extra memory usage.
The text was updated successfully, but these errors were encountered: