Why we shifted to monorepo from sub modules?

export interface IUser {
id: string;
name: string;
age: number;
...
}
public isMultiline(string: string): boolean {
return string.includes('\n');
}
  • I’ll create a sub module (or sub repo — having all the authentication implementation logic) and import it in all the three parent applications.
  • or I’ll copy paste the exact same code in three different applications.
Photo by Tachina Lee on Unsplash
  • I revert the parents applications to previously released version
  • or I revert the sub module to previous version, and bump up the versions again for parent applications pointing to previous version of sub module to kick CI/CD and get the previous state of my submodule deployed. (as a new state for parent applications though).
Photo by Taylor Wright on Unsplash

--

--

--

Full stack engineer with expertise in angular/react, nest and graphql.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

MySQL JOINs

Tutorials On Docker-Part 15

April 21: Inside Cardstack This Week

High Definition Render Pipeline — Fog

Monitoring your Snowflake Organization with Snowsight

Apache Hive Beeline : Progress Bar

5 YouTube Channels DevOps Engineers Should Subscribe To

BETELGEUSE Unlocks the Infinite Potential of Web 3.0 Data Storage

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Saad Riaz

Saad Riaz

Full stack engineer with expertise in angular/react, nest and graphql.

More from Medium

Demystifying code splitting

TDD — Unit Testing TypeScript project with Jest

Resolving pitfalls of the ECMAScript class system

Understanding Target Dependencies in NX