For further actions, you may consider blocking this person and/or reporting abuse
Read next
Ng-News 24/46: Angular Camp, TypeScript 5.7 RC
ng-news -
Building and Comparing Table Data Made Easy with @libs-jd/table-data-kit
Jeet Dhandha -
Reliable Notification Systems: Implementing Dead Letter Queues with RabbitMQ and Node.js
Abhinav -
Mastering JavaScript Memory: A Beginner’s Guide to Stack and Heap
chintanonweb -
Top comments (2)
I'm not really sure what to answer. I usually create three folders:
server/with the backend code.web/with the frontend code.shared/with the code that I use both in the backend and frontend.I make sure to install all frontend dependencies as dev dependencies, and I use foreman to start the backend and run webpack with one command.
Is there anything in particular that you find complex or challenging about having backend and frontend code in the same repo?
I am doing a new architecture of the project it is React and NodeJs in the backend API. So I think Monorepo to the project is more convenient. And I would like to know how you are doing yours.