-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: remove es5 tsconfig files #8203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: remove es5 tsconfig files #8203
Conversation
devversion
commented
Nov 3, 2017
- Makes use of the new overrides feature of the Angular Compiler CLI v5.
- Builds ES5 and ES2015 in parallel.
ed9fd4c
to
23b0439
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Makes use of the new overrides feature of the Angular Compiler CLI v5.
23b0439
to
288eec6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
const ngcFlags = ['-p', entryPointTsconfigPath]; | ||
|
||
if (es5OutputPath) { | ||
ngcFlags.push('--outDir', es5OutputPath); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can combine these into a single push: ngcFlags.push('--outDir', es5OutputPath, '--target', 'ES5')
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, I just wanted to keep it separate since those are two different option-value pairs and this way it feels more readable.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |