carpediem

PostsComments

NNuxt

•Created by carpediem on 7/4/2024 in #❓・help

Load composable on-demand

I'm afraid that encapsulating this kind of logic in components will make my application even heavier 😅 My app is a Portfolio, Wallet and Blockchain Explorer, so 3 app in one 😬 and therefore dependent on many different libraries for many different actions that can be executed only under certain conditions, on the client side

9 replies

NNuxt

•Created by carpediem on 7/4/2024 in #❓・help

Load composable on-demand

And I don't really see the point of composables if they have to be encapsulated in components to be used "on demand"

9 replies

NNuxt

•Created by carpediem on 7/4/2024 in #❓・help

Load composable on-demand

This is indeed already the case, but I don't think it's possible to encapsulate all heavy composables in components. The code above seems to work well and does what I'm looking for... I hope it won't have any undesirable side effects.

9 replies

NNuxt

•Created by carpediem on 7/4/2024 in #❓・help

Load composable on-demand

Like a LazyComponent... but for composable.

9 replies

NNuxt

•Created by carpediem on 7/4/2024 in #❓・help

Load composable on-demand

This is the case. But the composable is loaded when the page loaded instead of when needed (eg. when clicking on Wallet button), hence the need to load the composable on demand. Am I clear? 😕

9 replies