-
Notifications
You must be signed in to change notification settings - Fork 12k
feat(@schematics/angular): update compiler options target and module settings #17630
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,7 +32,8 @@ export enum ThresholdSeverity { | |
} | ||
|
||
enum DifferentialBuildType { | ||
ORIGINAL = 'es2015', | ||
// FIXME: this should match the actual file suffix and not hardcoded. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 😮 |
||
ORIGINAL = 'es2016', | ||
DOWNLEVEL = 'es5', | ||
} | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -126,7 +126,7 @@ describe('bundle-calculator', () => { | |
{ | ||
name: '0', | ||
original: { | ||
filename: 'foo-es2015.js', | ||
filename: 'foo-es2016.js', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh uh. I didn't realize that we will start renaming the files in dist/ as well. Hmm. This file rename will break a lot of stuff in angular/angular (e.g size tracking) and invalidate docs guides. Let's back off on the es2016 change and keep only the modules change. In v11 we can create a proper plan for target=es2016 or maybe even higher (zones!). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we might want to name the files something more generic maybe instead of the syntax version. |
||
size: 1.25 * KB, | ||
}, | ||
downlevel: { | ||
|
@@ -141,7 +141,7 @@ describe('bundle-calculator', () => { | |
expect(failures.length).toBe(2); | ||
expect(failures).toContain({ | ||
severity: ThresholdSeverity.Error, | ||
message: jasmine.stringMatching('Exceeded maximum budget for foo-es2015.'), | ||
message: jasmine.stringMatching('Exceeded maximum budget for foo-es2016.'), | ||
}); | ||
expect(failures).toContain({ | ||
severity: ThresholdSeverity.Error, | ||
|
@@ -170,7 +170,7 @@ describe('bundle-calculator', () => { | |
name: '0', | ||
// Individual builds are under budget, but combined they are over. | ||
original: { | ||
filename: 'foo-es2015.js', | ||
filename: 'foo-es2016.js', | ||
size: 0.5 * KB, | ||
}, | ||
downlevel: { | ||
|
@@ -240,7 +240,7 @@ describe('bundle-calculator', () => { | |
name: '0', | ||
// Individual builds are under budget, but combined they are over. | ||
original: { | ||
filename: 'initial-es2015.js', | ||
filename: 'initial-es2016.js', | ||
size: 1.25 * KB, | ||
}, | ||
downlevel: { | ||
|
@@ -255,7 +255,7 @@ describe('bundle-calculator', () => { | |
expect(failures.length).toBe(2); | ||
expect(failures).toContain({ | ||
severity: ThresholdSeverity.Error, | ||
message: jasmine.stringMatching('Exceeded maximum budget for initial-es2015.'), | ||
message: jasmine.stringMatching('Exceeded maximum budget for initial-es2016.'), | ||
}); | ||
expect(failures).toContain({ | ||
severity: ThresholdSeverity.Error, | ||
|
@@ -283,7 +283,7 @@ describe('bundle-calculator', () => { | |
name: '0', | ||
// Individual builds are under budget, but combined they are over. | ||
original: { | ||
filename: 'initial-es2015.js', | ||
filename: 'initial-es2016.js', | ||
size: 0.5 * KB, | ||
}, | ||
downlevel: { | ||
|
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.
Have you verified that the oldest version of node that we support is compatible with full es2018? I think it might be but I'm not sure.
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.
The oldest Node version that we support is
10.13.x
, it seems that the only thing which is not supported is https://tc39.es/ecma262/#sec-proxy-object-internal-methods-and-internal-slots-ownpropertykeysSee: https://node.green/#ES2018