How to keep an express server and React front-end in one repo?

• sb

  2 2 0.0 JavaScript

  Single-page application boilerplate.

I have a boilerplate setup for this. Takes some getting used to, but feel free to check it out: sb

• devconnector_2.0

  4 1,891 0.0 JavaScript

  Social network for developers, built on the MERN stack

Github: https://github.com/bradtraversy/devconnector_2.0

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• crisp-react

  24 185 0.0 TypeScript

  React boilerplate written in TypeScript with a variety of Jamstack and full stack deployments. Comes with SSR and without need to learn a framework. Helps to split a monolithic React app into multiple SPAs and avoid vendor lock-in.

One repository is enough: example. The most important thing is not the number of repositories but rather the number of webservers you run in production. Having one server instead of two lets you cut the complexity of the deployment, reduce its cost and improve security since two servers have larger exposure and with one server you don't need to use CORS which weakens security.

Suggest a related project