Build using TypeScript project references #1984
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The performance of project references is at a level where we can actually use them now, this change vastly simplifies out build process by essentially having a "solution" file whose job it is to build the other sub-projects (xterm.js and the addons). The dependencies look like this:
The vision here is that once the layering refactor is complete for it to look like this:
Other things this PR does:
concurrently
which will fix yarn is eating following commands #1639, part of this was moving the demo to depend on src/ directly instead of build/yarn watch
which will also watch for changes in addons and update that project only if a file change occursFixes #1337
Fixes #1639