Advice on Tech Stack and Project Structure for My New Website

0
3
Asked By CuriousCactus42 On

Hey everyone! I'm diving into a new project to create a website for a hobby I share with my friends. I'm all set on using TypeScript and React for the front end, but I'm a bit unsure about the back end. I want to use Node.js, specifically Fastify, since I haven't worked with it much before and think it could be beneficial.

However, I'm kind of lost when it comes to how to structure my projects. I'm leaning toward a monorepo setup with Lerna because I heard it can help manage deployments better, especially for platforms like Heroku. But I'm worried I might be overcomplicating things. Should I stick with one repo or split them up? I want to avoid paying for multiple servers once the site is up and running. I'd really appreciate any tips or insights you guys might have!

2 Answers

Answered By CodeWizardX On

Stick with the monorepo idea! Node.js is a solid choice for your back end. It might seem challenging, but since you're already familiar with TypeScript and React, you should pick up Node quickly. Maybe ask for project structure advice from ChatGPT or experiment with Go if you're feeling adventurous too!

Answered By DevDude22 On

Hey! I totally get how overwhelming this can be. Here’s the deal:

1. You only need one server for both front end and back end right now. Think of them as parts of the same application.
2. Start with a single repo that has two folders—one for your front end and one for your back end. You can scale up later if you need to.
3. If your project grows in complexity, check out pnpm workspaces for managing packages without getting tied into something like Lerna. It's easier and keeps dependencies in check!

CuriousCactus42 -

That sounds like a solid plan! I will check out pnpm workspaces. Thanks for the detailed breakdown!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.