Skip to content

ivanbaha/team-workspace

Repository files navigation

Team Workspace

Central monorepo for the development team. All frontend microfrontends, backend services, infrastructure configs, and shared documentation live here.


Workspace Structure

  • frontend — Frontend projects (microfrontends and host app)
  • backend — Backend services
  • libs — Internal shared libraries (UI primitives, API clients, common middleware)
  • infra — Infrastructure configuration and GitOps
  • docs — Shared team documentation
  • scripts — Workspace automation scripts
  • configs — Workspace-level configuration files

Quick Navigation

Frontend

Backend

Infrastructure

Libraries

  • libs/README.md — Internal shared libraries
    • tw-common-frontend — Shared React hooks, context providers, and UI primitives
    • tw-api-client — Typed HTTP client wrappers for all internal REST APIs
    • tw-common-backend — Shared Express middleware, JWT utilities, and error helpers
    • tw-config — Centralised environment variable loader and schema validation

Scripts and Config

Documentation


Getting Started

# 1. Clone all repos listed in configs/workspace-repos.json and install the git hook
yarn setup

# 2. Install all workspace dependencies
yarn install

# Run the host frontend in development mode
yarn dev:host

# Run a specific backend service
yarn dev:users-be

# Pull updates in all nested repos (also runs automatically after git pull)
yarn update

After running yarn setup once, a post-merge git hook is active. Every subsequent git pull on the workspace will automatically call yarn update to keep all nested repos in sync.

Refer to each project's own README for detailed instructions.


VS Code Settings

A .vscode/settings.json file is committed to this repository. Do not remove it.

The most important setting it enforces is:

"git.detectSubmodules": false

VS Code's Source Control panel continuously scans for Git repositories inside the workspace. With a large number of nested repos cloned by yarn setup, this background scanning becomes extremely resource-intensive — slowing down the editor and flooding the Source Control view with unrelated repo states. Disabling submodule detection stops this entirely without affecting any other Git functionality.

About

A demo project for showcasing configuration of a coding workspace for teams

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors