Kubilay Melnikov

@mercs600 that is already possible, you close the issue?

@mercs600 this would be my first idea, would that be okay? /nuxt-typo3/lib/templates/plugins/components.js ``` export default (context, { registerComponents }) => { Object.keys(components) .filter( key => (typeof registerComponents === 'boolean' &&...

@mercs600 you mean something like this: // variant 1 ``` export default (context, { registerComponents }) => { import from '~typo3/components/utilities/.vue' Vue.component('', ) } ``` // variant 2 ``` export...

@mercs600 it is not the most beautiful way... The large object bothers me, i would prefer to move this to another file.

Here's a glimpse into the "quick" frontend solution, although it's not final! - The structure still needs to be adapted to the new version. - A new observer should not...

I have released the version [1.1.1](https://github.com/wineworlds/image-on-demand-service/tree/1.1.1) With an adapted URL structure and a caching.

Here is my temporary solution in the frontend: `src/components/Util/UtilImageOnDemand.vue` ```vue import type { T3File } from '@t3headless/nuxt-typo3' interface UtilImageOnDemand { image?: T3File type?: string lazy?: boolean dummy?: boolean text?: string...

@lukaszuznanski & @mercs600 There are still a few issues & questions... - What happens to the generated images: Is there a routine in place that deletes images that haven't been...

> @mercs600 please take a look at frontend solution, is this suitable for us? Another possibility could be to only provide the composable to generate the link. In the end,...

@mercs600; I have now written a composable function. I believe this is the right approach if you'd like to include it. I'm also happy to create a Pull Request in...