ember-cli-typescript - npm Package Versions

[2.0.0-rc.2] - 2019-01-07

For details on the changes since 1.x, see the 2.0.0-beta.1 release notes.

Fixed 🔧

• Set --isolatedModules back to false in both precompilation and generated blueprints

Added ⭐️

• We now warn you nicely if you try to use this in an addon via devDependencies instead of dependencies

Under the hood 🚗

• Used the same tests commands across providers, so we get the same results

Upgrading ⚙️

For apps:

ember install ember-cli-typescript@next

For addons:

ember install -S ember-cli-typescript@next

Contributors 🙇

Thanks to everyone who opened/discovered an issue we fixed or PR we merged in this release!

• @alexlafroscia
• @dfreeman
• @happycollision

[2.0.0-rc.1] - 2018-12-13

What Changed?

For details on the changes since 1.x, see the 2.0.0-beta.1 release notes.

Fixed 🔧

• Builds no longer hang if a changed TypeScript file did not trigger a TS rebuild (which can happen e.g. if it is not yet imported elsewhere).
• Type-checking information now properly gets injected into the build pipeline for test builds as well as development and production builds.
• Declaration maps now have test coverage to make sure they don't break.

Changed 💥

• The build system now uses the tsconfig.json file's paths key to copy type definitions during precompile, rather than assuming Ember project structure.

Added ⭐️

• The addon now checks to confirm you're using Ember CLI 3.5+, since the new approach to builds has serious performance problems with a local tmp directory.

Under the hood 🚗

• Bumped many dependency versions.
• Set up Azure Pipelines configuration.
• Updated internals to use TypeScript themselves.

Upgrading ⚙️

ember install ember-cli-typescript@next

Contributors 🙇

Thanks to everyone who opened/discovered an issue we fixed or PR we merged in this release!

• @mike-north
• @dfreeman
• @jamescdavis

[2.0.0-beta.3] - 2018-11-02

What Changed?

For details on the changes since 1.x, see the 2.0.0-beta.1 release notes.

Fixed 🔧

• Ensure consistency with tsc re: class property initialization order (#365)

Upgrading ⚙️

ember install ember-cli-typescript@beta

Contributors 🙇

Thanks to everyone who opened/discovered an issue we fixed or PR we merged in this release!

• @runspired
• @dfreeman

[2.0.0-beta.2] - 2018-10-26

Fixed

• Ensure that ember-cli-typescript doesn't interfere with parallelizing the Babel transpilation process (#351)

[1.5.0] - 2018-10-25

Fixed

• We now provide better user feedback when installing ember-cli-typescript from a git version (i.e. for testing prereleases)
• Updated to ember-cli-typescript-blueprints so types in generated files correctly match the latest Ember Data types
• Updated to latest Ember CLI blueprint (as of 3.5.0)

[2.0.0-beta.1] - 2018-10-25

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. ⚡️

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.)

THIS IS A BETA! Please test this out in your apps! Please do not use this for your production apps!

Added

• Much nicer reporting of type errors both in the console and in your browser
• Type errors now use the "pretty" type error format stabilized in TypeScript 2.9

Changed

• 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:

  • const enum types are unsupported. You should switch to constants or regular enums.

  • trailing commas after rest function parameters (function foo(...bar[],) {}) are disallowed by the ECMAScript spec, so Babel also disallows them.

  • re-exports of types have to be disambiguated to be types, rather than values. Neither of these will work:

    export { FooType } from 'foo';
    

    import { FooType } from 'foo';
    export { FooType };
    

    In both cases, Babel attempts to emit a value export, not just a type export, and fails because there is no actual value to emit. You can do this instead as a workaround:

    import * as Foo from 'foo';
    export type FooType = Foo.FooType;
    

  • this types in ES5 getters and setters are do not work (babel/babel#8069)

  • destructuring of parameters in function signatures currently do not work (babel/babel#8099)

  Other bugs you should be aware of:

  • if an enum has a member with the same name as an imported type (babel/babel#8881)

• ember-cli-typescript must be in dependencies instead of devDependencies for addons, since we now hook into the normal Broccoli + Babel build pipeline instead of doing an end-run around it

• Addons can no longer use .ts in app, because an addon's app directory gets merged with and uses the host's (i.e. the other addon or app'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. the app's, not the addon's) preprocessors.

• Apps need to use .js for overrides in app, since the different file extension means apps no longer consistently "win" over addon versions (a limitation of how Babel + app merging interact) – note that this won’t be a problem with Module Unification apps

Fixed

• Type errors now show properly in the browser when running tests

[1.4.4] - 2018-10-01

Fixed

• We no longer claim the absolute highest priority when ember-cli is selecting blueprints (see [#323])

[1.4.3] - 2018-09-24

Fixed

• We now correctly clean up the system temp directory we create during builds (see [#318])

Changed

• We reference the Discord channel instead of Slack.
• [Internal] We enabled writing code for this addon itself in TypeScript.

[1.3.4] - 2018-09-24

Fixed

• We now correctly clean up the system temp directory we create during builds. (Backported from 1.4.3; see [#318].)

[1.2.2] - 2018-09-24

Fixed

• We now correctly clean up the system temp directory we create during builds. (Backported from 1.4.3; see [#318].)