Releases · TypeStrong/ts-loader

20 Oct 10:02

johnnyreilly

v3.0.4

bb0b09d

v3.0.4

Chore release; upgraded chalk dependency to 2.2.0. - thanks @johnnyreilly

Assets 2

18 Oct 14:17

johnnyreilly

v3.0.3

81d02db

v3.0.3

Fix allowJs @types resolution error (#657, #655) - thanks @johnnyreilly and @roddypratt + @ldrick for providing minimal repro repos which allowed me to fix this long standing bug!

This fix resolves the issue for TypeScript 2.4+ (which is likely 95% of users). For those people stuck on 2.3 or below and impacted by this issue, you should be able to workaround this by setting entryFileCannotBeJs: true in your ts-loader options. This option should be considered deprecated as of this release. The option will likely disappear with the next major version of ts-loader which will drop support for TypeScript 2.3 and below, thus removing the need for this option.

Assets 2

16 Oct 14:40

johnnyreilly

v3.0.0

b70d5af

v3.0.0

All changes were made with this PR - thanks @johnnyreilly

Published to npm as v3.0.2 due to npm publishing issues - thanks @mattlewis92 for noticing!

drop support for typescript < 2.0 (no-one seems to be using it and we can simplify the code) BREAKING CHANGE
remove entryFileIsJs option; it can be inferred from whether the allowJs TypeScript compiler option has been set.
move to webpack 3.0 for test harness
drop configFileName support (replaced by configFile) BREAKING CHANGE
add support for a custom formatter for output - drop visual studio format (this can be added back if there's clamour for it and people can supply their own formatters in the interim) BREAKING CHANGE
make loglevel warn by default (stop outputting typescript version number by default). Fixes #488
fix tsc has "module" default to "es2015"when targetting es2015+, but ts-loader does not - thanks @Venryx for the suggestion!
switch to build ts-loader / run tests with yarn because of this
allow controlling whether the output can contain colours