Installing modules/Plugin during Runtime
Hello i hope you're having a good day.
Hello, this is mostly theoretical, i think it's mostly architectural but i'm not sure if it's feasible so bear with me.
So at work we have a white label application which we serve to multiple customers. And depending on the customer it has different skins for example
www.ourapp-cocacola.com will get coca cola skin etc etc ( Styling comes from information from backend)
Each page has 5 "menus" ( not sure how to call them )
Example naming
-) Buy
-) Rent
-) Sell
...
So next step is having specific features per customer for example. The user navigates to the Buy page. Somewhere on the page there's a "Buy Item" button.
Depending on the customer this button will navigate the user to a new page tailored to the customer needs. This page has to come from a "module" ( maybe a nuxt 3 module but what i want to say is from an outside source) or a plugin which will not be a part of the main application and will be installed/selected, during runtime.
The end goal is to provide features depending on the customer but we dont want to redeploy the app every time a new feature is added. But somehow have an outside source provide the page to the 5 of our pages.
So any thoughts on this? Is this feasible? Thank you for your time
2 Replies
Hi @Wicker. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Thank you for your question about Nuxt and dynamic module/plugin loading. This is an interesting architectural challenge for a white-label application. Based on the knowledge sources provided, I can offer some insights and suggestions, though the exact implementation you're looking for isn't directly covered in the available information.
1. Runtime Module/Plugin Installation:
Nuxt modules are typically installed and configured at build time, not runtime. The Nuxt Modules documentation states that "Nuxt modules are async functions that sequentially run when starting Nuxt in development mode using
nuxi dev or building a project for production with nuxi build". This suggests that dynamically installing modules at runtime is not a standard feature of Nuxt.
2. Dynamic Routing:
However, Nuxt does offer ways to implement custom routing, which could be leveraged for your use case. The Custom Routing documentation provides several methods to add or modify routes dynamically:
- Using the router.options.ts file to define custom routes
- Utilizing the pages:extend hook to add, change, or remove pages from the scanned routes
3. Layered Architecture:
Nuxt 3 introduces the concept of layers, which allows extending your application with reusable parts. The Layers documentation mentions that you can extend from npm packages or git repositories. This feature might be useful for organizing customer-specific components or pages.
4. Runtime Component Loading:
While not exactly what you're asking for, you might be able to achieve a similar result by dynamically loading Vue components at runtime. This could be done using Vue's dynamic component feature combined with Nuxt's auto-import capabilities.
5. Server-side Routing:
Another approach could involve using server-side logic to determine which components or pages to serve based on the customer. This could be implemented using Nuxt's server middleware or API routes.
Given these considerations, a potential approach could be:
1. Create a base application with the core functionality and the five main "menu" pages.
2. Develop customer-specific features as separate Vue components or Nuxt pages.
3. Use dynamic routing and component loading to serve the appropriate content based on the customer.
4. Store customer configurations (including which features to enable) in a database or configuration file that can be updated without redeploying the main application.
5. Implement server-side logic to determine which components to load based on the customer and requested route.
However, it's important to note that this approach would still require some form of deployment or update mechanism for new features, even if it doesn't require redeploying the entire application.
For a more detailed and tailored solution, you might need to explore advanced Nuxt features or consider additional technologies that could complement Nuxt in achieving your specific requirements. The provided knowledge sources don't contain enough information to fully address the dynamic module/plugin installation at runtime as you've described it.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@142400234444685312> Kapa.ai is still learning and improving, please let me know how I did by reacting below.