https://github.com/guidsdo/multipletypescriptcompilers
Monorepo solution for multiple typescript projects (tslint support!). Run multiple typescript compilers concurrently at the same time. Usage: `mtsc [directories...]` Example: `mtsc client server middleware`
https://github.com/guidsdo/multipletypescriptcompilers
Last synced: about 1 year ago
JSON representation
Monorepo solution for multiple typescript projects (tslint support!). Run multiple typescript compilers concurrently at the same time. Usage: `mtsc [directories...]` Example: `mtsc client server middleware`
- Host: GitHub
- URL: https://github.com/guidsdo/multipletypescriptcompilers
- Owner: guidsdo
- License: apache-2.0
- Created: 2017-08-27T15:34:05.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2024-09-12T08:40:13.000Z (almost 2 years ago)
- Last Synced: 2025-04-13T11:42:28.933Z (about 1 year ago)
- Language: TypeScript
- Homepage:
- Size: 728 KB
- Stars: 18
- Watchers: 1
- Forks: 0
- Open Issues: 12
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Multiple Typescript Compilers 
_Monorepo solution for multiple typescript projects. Watch multiple typescript compilers concurrently at the same time, without losing output!_
[](https://travis-ci.org/guidsdo/multipleTypescriptCompilers)
[](https://coveralls.io/github/guidsdo/multipleTypescriptCompilers?branch=master)
[](https://snyk.io/test/github/guidsdo/multipleTypescriptCompilers)
[](https://david-dm.org/guidsdo/multipleTypescriptCompilers)
[](https://www.npmjs.com/package/mtsc)
[](https://www.npmjs.com/package/mtsc)
[](https://github.com/prettier/prettier)
The vision and goal for Mtsc is, and always has been, the following:
- Be able to lint and ts-compile multiple projects, concurrently whilst keeping all the results (not possible with just `concurrently`)
- Facilitate proper vscode integration which means:
- See lint and tsc result without having to open a specific file
- Require the least amount of necessary configurability
- Support mono-repo's natively
- Support the following workflow:
1. Clone a project
1. `yarn`
1. `code .`
1. `cmd+shift+b`
1. See what's happening in your whole monorepo and be able to work at the same time (watchmode). :mindblown:
## Usage
**NOTE: Supported versions: Typescript 2.8+. Use Mtsc 1.\* for older versions**
### Cli:
`mtsc [directories/tsconfigs...]`
### Examples:
`./node_modules/.bin/mtsc client scripts/ide.tsconfig.json special/location`
`mtsc client scripts/ide.tsconfig.json special/location -w`
`mtsc -c client/tsconfig.json scripts/ide.tsconfig.json -w`
`mtsc -c node_modules/.bin/tsc client/tsconfig.json scripts/ide.tsconfig.json -w`
## Why?
I began this project because vscode can't handle the output of multiple typescript projects. If you have multiple projects watched at the same time, only the output of the last compilation will be considered and the other errors of other projects are hidden. This has to do, with the problem matcher vscode uses, explained here: https://code.visualstudio.com/docs/editor/tasks-v1#_background-watching-tasks
### How it was fixed:
This always prints the compilation output of the other projects when a new compilation is done. It also makes sure that the interpreter knows there is still a compilation going on by printing a compilation start message when there is still one running.
### Known issues
- Please let me know
## Cli
```
Usage: mtsc [options] [projects/tsconfigs...]
Options:
-d, --debug Add way too much logging
-c, --config [path_to_config] Path to mtsc config
-w, --watch Watch the given projects (default false)
-t, --tsc [path_to_tsc] Path to compiler for all projects (will search in exec dir if not given)
--noEmit Do not emit outputs
-h, --help output usage information
```
## mtsc.json spec
[Config spec can be seen here](https://github.com/guidsdo/multipleTypescriptCompilers/blob/master/src/config/configSpec.ts)
## Vscode integration
Set the typescript compiler in vscode by clicking on the compiler version. This is only possible when you open a typescript file. This setting sometimes goes to the builtin vscode compiler, so if you don't see errors; check this first.
## Vscode tasks json examples
### Example using cli only
```json
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "Mtsc",
"command": "./node_modules/.bin/mtsc -w projectA scripts/projectB projectC/tsconfig.json",
"isBackground": true,
"problemMatcher": "$tsc-watch",
"group": {
"kind": "build",
"isDefault": true
},
"runOptions": {
"runOn": "folderOpen"
}
}
]
}
```
### Example using CLI + config
`tasks.json`
```json
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "Mtsc",
"command": "./node_modules/.bin/mtsc",
"isBackground": true,
"problemMatcher": "$tsc-watch",
"group": {
"kind": "build",
"isDefault": true
},
"runOptions": {
"runOn": "folderOpen"
}
}
]
}
```
`mtsc.json` (will be autodetected)
```json
{
"debug": false,
"watch": true,
"projects": ["projectA", "scripts/projectB", "projectC/tsconfig.json"]
}
```
## Roadmap
- Any ideas? Let me know :)
---
**Mtsc is proudly used for development at [Mendix](https://www.mendix.com)**