-
We are wanting to go a more modular way of dividing our application, but we have no intention of wrapping each module as a package, with its own package.json and composer.json packages. So the question is, can we strip out all the folders we do not need? We do tend to keep something generic, like master layouts. Base methods and services. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
You can remove composer.json, package.json and vite.config but you will need to keep module.json as this is required to load the module's service provider. |
Beta Was this translation helpful? Give feedback.
-
This is how I normally work, route assets and packages through base Laravel and treat modules like sections to store related code. |
Beta Was this translation helpful? Give feedback.
You can remove composer.json, package.json and vite.config but you will need to keep module.json as this is required to load the module's service provider.