Weather monorepo

Sample monorepo with two Typescript applications:

• wether-server. Sample express web Api. Exposes a weather random data endpoint (i.e. /api/weather) and serves the weather-client React web app in the root url (by copying the UI static files in the public folder).

• wether-client. Sample React web app. Consumes the weather-server web Api and displays the returned weather data.

Each project has it's own package.json, with specific dependencies and scripts. The root package.json file is used for common dependencies, repository setup (i.e. husky and dependencies installation) and cross-project scripts (i.e. formatting validation and static assets deployment).

Motivation

The goal of this repository is to illustrate different ways of structuring interdependent Typescript projects. Several approaches are considered:

main
|
└─ base-code-extraction
   |
   ├─ 1-path-fixes
   |
   └─ 2-npm-project
      |
      ├─ 3-local-dependency
      |
      ├─ 3-local-dependency-namespace
      |
      ├─ 4-npm-workspaces
      |
      └─ 4-npm-workspaces-namespace

• main. Single monorepo combining interdependent individual repositories (i.e. weather-client and weather-server). At this stage only repository settings (e.g. prettier, husky, VSCode settings and and all-projects .gitignore folders) and runtime settings (e.g. all-projects tsconfig.json properties and all-projects dependencies) are shared.

• base-code-extraction: The duplicated Typescript code is extracted into a weather-common folder and imported from both weather-client and weather-server using relative imports. Introduces runtime errors that will fix it in following branches.

• 1-path-fixes. Fixing the runtime errors by adapting relative paths that Typescript compilation modifies.

• 2-npm-project. Fixing the runtime errors by turning the weather-common folder into an npm project.

• 3-local-dependency. Fixing the runtime errors by turning the weather-common folder into an npm project and replacing the relative path imports with npm local dependencies.

• 3-local-dependency-namespace. Same as 3-local-dependency but renaming the npm packages and changing the folder structure to use the @weather namespace beforehand.

• 4-npm-workspaces. Fixing the runtime errors by turning the weather-common folder into an npm project and replacing the relative path imports with npm workspaces.

• 4-npm-workspaces-namespace. Same as 4-npm-workspaces but renaming the npm packages and changing the folder structure to use the @weather namespace beforehand.