You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the repository has separate run scripts for the frontend and backend (npm run dev: frontend and npm run dev: backend respectively), even though both scripts essentially do the same thing (npm run dev). This duplication in run scripts adds unnecessary complexity to the project setup and maintenance.
The text was updated successfully, but these errors were encountered:
Another viable approach to address this issue is serving the SPA (Single Page Application) files directly from the backend after building them using npm run build. Here's a pull request that implements this alternative method: #1084 . This solution not only simplifies the setup but also streamlines maintenance efforts. It's worth considering for enhancing the project's efficiency and maintainability.
I checked your pull request, I think that it may lead to increased server load, especially for large applications, and can make it harder to scale the frontend and backend independently.
Currently, the repository has separate run scripts for the frontend and backend (npm run dev: frontend and npm run dev: backend respectively), even though both scripts essentially do the same thing (npm run dev). This duplication in run scripts adds unnecessary complexity to the project setup and maintenance.
The text was updated successfully, but these errors were encountered: