ES3 runtimes are increasingly few and far between, and many common features (getters and setters, spread in new) only work in ES5. The 2.0 release would be a good time to take a BC break to update the default target to ES5.
Related, and somewhat confusingly, we emit a tsconfig.json with target: ES5 when running tsc --init even though the actual default target is ES3. We should at least be consistent here.
ES3 runtimes are increasingly few and far between, and many common features (getters and setters, spread in
new) only work in ES5. The 2.0 release would be a good time to take a BC break to update the default target to ES5.Related, and somewhat confusingly, we emit a
tsconfig.jsonwithtarget: ES5when runningtsc --initeven though the actual default target is ES3. We should at least be consistent here.