Clasp: [RFC] Best practices for managing Apps Script monorepos

[PopGoesTheWza]

Purpose of this issue is to discuss and exchange on how one handle Apps Script monorepos:

• current solutions
• key features/functionalities
• missing features/functionalities

[imthenachoman]

I'm curious how this ties or is dependent to clasp. Are you talking about if someones got many projects in one GAS file or if someone is putting many projects into a single GitHub/GitLab repo?

[PopGoesTheWza]

Typically, a single repository composed of several projects which share common resources (i.e. code)

I have this starter template which I'll be updating for v8 support soon.

[imthenachoman]

I see. So multiple GAS projects in one TS project that each get pushed to their own GAS project? I se great value in this. Especially for "common libraries".

[contributorpw]

If you allow me.

I use an approach based on the clasp. It uses gulp & cli flows.

I do not know the current version supports multiple project files, so I just swap the .clasp.json file to redirect the stream to a project https://github.com/hedgehogsburrows/empty-google-apps-script-project/blob/master/gulpfile.js#L63-L74.

Based on this approach I also use the spread distribution of one code for several projects, when I create a series of consecutive pushes.

I also use "reverse code support" so that the customer can make changes directly to the project.

I try to avoid monorepos for transparent and lightweight projection.

I also use classes (or old-style modules) from external loosely coupled sources for assembly or bundles https://github.com/contributorpw/google-apps-script-snippets/blob/master/gulpfile.js#L35

If any of this is helpful let me know I will do a practice.