@metalsadman and @dnix thank you for reply. I use a quasar ext for common sections such as components, boots, stores and etc. Each new project have own pages and other uncommon sections.All of them use this extension.
Posts made by mohamadJ
RE: How to handle projects which have common sections
RE: Can we get props from quasar.config.js? (0.15)
you can use let ctx = require(‘path/quasar.conf.js’) for import conf file in your js files.then use ctx().foo for access foo in quasar.conf.js
How to handle projects which have common sections
I have a project created with quasar-cli. Now, I want to make some projects Which are almost similar to this project ,however, it also faces with some differences in pages,routes,stores and etc. These projects will definitely become updated in common and separate sections. The question is that what will be the best solution for handle such projects in case of saving time and coding?