Is it safe to set the tsconfig target to es6 if you don't care about old browsers?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
In an Angular application, is it safe to set the tsconfig.json
compilerOptions.target to "es6"
(or the equivalent "es2015"
) if you don't care about old browsers?
About this matter, in the official Angular documentation is written:
By default, the target is es5, you can configure the target to es6 if you only want to deploy the application to es6 compatible browser. But if you configure the target to es6 in some old browser such as IE, Syntax Error will be thrown.
So assuming that I do want to deploy my application only to es6 compatible browsers ONLY, should I just set the compile target to es6
Are there any other concerns I should be aware of?
For example, some Angular third-part libraries start not working and throw the notorious error:
TypeError: Class constructors cannot be invoked without 'new'
is it correct to assume that in these cases there is a bug in such third-part library?
angular typescript ecmascript-6 es6-class angular-library
add a comment |
In an Angular application, is it safe to set the tsconfig.json
compilerOptions.target to "es6"
(or the equivalent "es2015"
) if you don't care about old browsers?
About this matter, in the official Angular documentation is written:
By default, the target is es5, you can configure the target to es6 if you only want to deploy the application to es6 compatible browser. But if you configure the target to es6 in some old browser such as IE, Syntax Error will be thrown.
So assuming that I do want to deploy my application only to es6 compatible browsers ONLY, should I just set the compile target to es6
Are there any other concerns I should be aware of?
For example, some Angular third-part libraries start not working and throw the notorious error:
TypeError: Class constructors cannot be invoked without 'new'
is it correct to assume that in these cases there is a bug in such third-part library?
angular typescript ecmascript-6 es6-class angular-library
Is it a "bug" if something that has worked becomes invalid due to a language update?
– Henry
Nov 16 '18 at 14:18
add a comment |
In an Angular application, is it safe to set the tsconfig.json
compilerOptions.target to "es6"
(or the equivalent "es2015"
) if you don't care about old browsers?
About this matter, in the official Angular documentation is written:
By default, the target is es5, you can configure the target to es6 if you only want to deploy the application to es6 compatible browser. But if you configure the target to es6 in some old browser such as IE, Syntax Error will be thrown.
So assuming that I do want to deploy my application only to es6 compatible browsers ONLY, should I just set the compile target to es6
Are there any other concerns I should be aware of?
For example, some Angular third-part libraries start not working and throw the notorious error:
TypeError: Class constructors cannot be invoked without 'new'
is it correct to assume that in these cases there is a bug in such third-part library?
angular typescript ecmascript-6 es6-class angular-library
In an Angular application, is it safe to set the tsconfig.json
compilerOptions.target to "es6"
(or the equivalent "es2015"
) if you don't care about old browsers?
About this matter, in the official Angular documentation is written:
By default, the target is es5, you can configure the target to es6 if you only want to deploy the application to es6 compatible browser. But if you configure the target to es6 in some old browser such as IE, Syntax Error will be thrown.
So assuming that I do want to deploy my application only to es6 compatible browsers ONLY, should I just set the compile target to es6
Are there any other concerns I should be aware of?
For example, some Angular third-part libraries start not working and throw the notorious error:
TypeError: Class constructors cannot be invoked without 'new'
is it correct to assume that in these cases there is a bug in such third-part library?
angular typescript ecmascript-6 es6-class angular-library
angular typescript ecmascript-6 es6-class angular-library
asked Nov 16 '18 at 13:44
Francesco BorziFrancesco Borzi
15.5k95994
15.5k95994
Is it a "bug" if something that has worked becomes invalid due to a language update?
– Henry
Nov 16 '18 at 14:18
add a comment |
Is it a "bug" if something that has worked becomes invalid due to a language update?
– Henry
Nov 16 '18 at 14:18
Is it a "bug" if something that has worked becomes invalid due to a language update?
– Henry
Nov 16 '18 at 14:18
Is it a "bug" if something that has worked becomes invalid due to a language update?
– Henry
Nov 16 '18 at 14:18
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53339089%2fis-it-safe-to-set-the-tsconfig-target-to-es6-if-you-dont-care-about-old-browser%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53339089%2fis-it-safe-to-set-the-tsconfig-target-to-es6-if-you-dont-care-about-old-browser%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is it a "bug" if something that has worked becomes invalid due to a language update?
– Henry
Nov 16 '18 at 14:18