Asset strategy

[jonaskuske]

Currently all assets imported in the frontend portion are included in the JS/CSS files as data URLs. This means that importing a single image can blow up the size of the JS to be parsed and executed to multiple MBs!

Would be great to somehow skip inlining the assets, but it doesn't appear that easy to solve, as the problematic behavior is built into Vite and not configurable:

• https://vitejs.dev/config/build-options.html#build-assetsinlinelimit
• add an option to not to inline assets in library mode when format is 'es' vitejs/vite#4454
• library mode can't extract static assets vitejs/vite#3295
• feat: build library new option - emitAssets vitejs/vite#5028

Optimal would be some integrations so assets are loaded from the plugin's assets/ folder which Kirby automagically copies to the /media directory: https://getkirby.com/docs/guide/plugins/plugin-basics#plugin-assets

[johannschopplich]

Kirby actually copies assets from a plugin's assets folder to the media folder already.

As it says in your opening post. Pardon me. 😅