Backend (VueJS) of laravel application with modules approach

问题

I come to you to take information on how to guide my development.

I'm developing an application with modules approach.

Current architecture:

app
bootstrap
config
modules
    auth
    backend
    cms
    Core
    ...
public
...

I work on administration (backend module). Each module has its composer.json and therefore a repository github (each module has its own version).

I don't know how to orient myself for the backend part.

Do I have to go to a VueJS multi-application solution? Each module would have an architecture of this type:

ModuleName / Resources / Backend / Assets / js
ModuleName / Resources / Backend / Assets / js / app.js
ModuleName / Resources / Backend / Assets / js / components /
ModuleName / Resources / Backend / Assets / js / views /
ModuleName / Resources / Backend / Assets / sass /
...

The "Backend" module would have a default .blade layout.

Or a SPA solution? Managed by the "Backend" module.

And do you think using VueJS for the admin part is a good idea?

Thank you! :)

来源：https://stackoverflow.com/questions/57673764/backend-vuejs-of-laravel-application-with-modules-approach

标签

laravel