How to organize a family of Quasar-based projects that are using common/internal components & modules
jaguard last edited by
I’m in process of developing a “family” of projects for which I’ve considered Quasar being the best options.
Here are the “individual” projects:
1 x Cordova ClientApp: Android/iOS mobile application used by regular users (include BT/BLE support)
2 x Cordova AdminApp: Android/iOS mobile application used by admins
1 x SPA Dashboard: web application used by support
1 x Electron TechnicianApp: Windows desktop app (with off-line support) with BT/bleno integration
Aside of specialized functionality in all these apps, there are some common functionality and components that I want to reuse, so some modularization by introducing common “library” kind of modules should be used (ex: using FIrebase + authentication + login component, common store/module for user management …etc).
Maybe the optimal solution is not necessary Quasar specific, but the issue is more generic and may apply to VueJS shared projects as well … The idea is to avoid exposing & publishing internal components as Node modules to be imported in other “consumer” projects …
I had various ideas like using
npm/yarn linkto use internal modules without npm publishing or using a monorepo and yarn workspaces … but having a sample/template that really works it will be a lot better
Any suggestions , hints, links and refs will be highly appreciated … !