You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+66-1Lines changed: 66 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,69 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) a
6
6
7
7
## [Unreleased]
8
8
9
+
## [2.0.0-beta.1] - 2018-10-25
10
+
11
+
This is a major release with 💥 breaking changes 💥! However, most apps will compile with minimal (or no) changes! 🎉 They'll also tend to compile *much faster* in many cases. ⚡️
12
+
13
+
We now use Babel 7's support for TypeScript to build apps and addons. Most of the horrible hacks we had to do before are now gone, and the error outputs you will see for type errors are much nicer as well. (As a particular note, we should work better with `ember-auto-import` now, since we're just part of the normal Broccoli/Babel pipeline Ember CLI uses.)
14
+
15
+
***THIS IS A BETA!*** Please test this out in your apps! Please do *not* use this for your production apps!
16
+
17
+
### Added
18
+
19
+
* Much nicer reporting of type errors both in the console and in your browser
20
+
* Type errors now use the "pretty" type error format stabilized in TypeScript 2.9
21
+
22
+
### Changed
23
+
24
+
* We now build the application using Babel 7's TypeScript plugin. This has a few important limitations – some of them bugs (linked below); others are conscious decisions on the part of Babel. The changes:
25
+
-`const enum` types are unsupported. You should switch to constants or regular enums.
26
+
27
+
- trailing commas after rest function parameters (`function foo(...bar[],) {}`) are disallowed by the ECMAScript spec, so Babel also disallows them.
28
+
29
+
- re-exports of types have to be disambiguated to be *types*, rather than values. Neither of these will work:
* Addonscannolongeruse`.ts`inapp, becauseanaddon's `app` directory gets merged with and uses the *host's* (i.e. theotheraddonorapp's) preprocessors, and we cannot guarantee the host has TS support. Note that in-repo-addons will continue to work for in-repo addons because of the app build works with the host's (i.e. theapp's, not the addon's) preprocessors.
0 commit comments