Dependencies among Typescript projects (within one repo)

Question

I have a series of Typescript projects (each an actual compilable target, with its own tsconfig.json). They are sibling directories within one code repository, like this:

myrepo
--/common
--/project1
--/project2

In order to share code between project1 and project2, I've broken some shared code out into common. I would like to allow project1 and project2 code to import classes from common, but not from each other (and common should not be able to import classes from either of the other two).

Ideally, code in project1 might look like this:

import {CommonClass} from 'common/commonclass';

I have found a way to allow the importing to work correctly, by putting this into the tsconfig.json of project1:

  "baseUrl":".",
  "paths":{
    "*":["*","../*"]
  }

However, I have not yet found a way to limit which of the other subprojects can be the subject of an import. I've tried using rootDirs, hoping that it would restrict the allowable source files in the same way rootDir does, but it actually does not.

How could I whitelist what code is importable in each of my projects? Or is there just some better way of building subprojects in Typescript that I'm not aware of?

Answer 1

I also had to deal with a similar structure and couldn't find an ideal way to do so.
The best I managed to come up with is having a lib directory in project1 and project2 which contains the compiled common alongside the definition files.

I used gulp to build the common project into the different projectX/lib directories:

gulp.task("common-project1", function () {
    var tsProject = ts.createProject("common/tsconfig.json");

    return tsProject.src("common/**/*.ts")
        .pipe(tsProject())
        .pipe(gulp.dest("project1/lib/common"));
});

It's not the best solution because it requires you to run this gulp task every time you change the common source, but I'v discovered that it doesn't happen very often once that common is stable enough.