Skip to content

Monorepo Architecture #291

@InvictusNavarchus

Description

@InvictusNavarchus

I came across this project recently and I really like the concept. Many of these tools are something we all do, and it's pleasant to have all of them in one place in just one click.

I want to contribute to this project, but I had a little bit of difficulty understanding the codebase. It seems you mixed 3 different independent project in one codebase.

  1. Vercel/Netlify functions, at api/
  2. Landing page at src/
  3. The actual web-check web app at src/web-check-live.

They all use different tech stack and different dependencies, yet they all inherit the same package.json, with various config and deployment setup at the root. It's hard to understand which one is for which.

I'd suggest splitting them into 3 separate folders. It's still a monorepo but with clear boundaries. Something like

  1. landing-page/
  2. app/
  3. api/

each with their own package.json and configs.
You can then tie them up together with turborepo from root so you can still run them all at once.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions