v4.0.1

• Fix name collision in experimentalWatchApi code - thanks @MLoughry!

v4.0.0

• Support webpack 4
• Drop support for webpack 2/3 BREAKING CHANGE - use ts-loader 3.x if you need webpack 2/3 support
• Minimum TypeScript version is now 2.4.1 BREAKING CHANGE
• Deprecated option entryFileCannotBeJs removed' BREAKING CHANGE
• Start using prettier for the codebase

v3.5.0

• Add trace for traceResolution - thanks @onigoetz!

v3.4.0

• local .d.ts files now marked as changed when watch is triggered - thanks @KnisterPeter!

v3.3.1

• Fixes to support watch api for compiling - lib support etc - thanks @sheetalkamat!

v3.3.0

• Report diagnostics only on certain files with reportFiles option - thanks @freeman!
• Replaced option contextAsConfigBasePath with context option. Strictly speaking a breaking change. However, given the original option was never able to fulfil its intended purpose I've decided to treat this as just a new feature; there seems no possibility that anyone can be using contextAsConfigBasePath - thanks @christiantinauer!
• Added support for the new watch api of TypeScript compiler. nb This feature has been placed behind a new experimentalWatchApi option until it has been thoroughly tested. All being well it is likely to become the default behaviour for ts-loader in future - thanks @sheetalkamat!

v3.2.0

• Add new loader option contextAsConfigBasePath - thanks @christiantinauer

v3.1.1

Fix error importing buildt ts files with allowJs (#667) - thanks @Pajn!

v3.1.0

• Add onlyCompileBundledFiles option which modifies behaviour to load only those files that are actually bundled by webpack #267 - thanks @maier49!
• Chore release; upgraded chalk dependency in package.json to 2.3, as 2.3 is another breaking changes release (from a TypeScript perspective)., see here for context - thanks @johnnyreilly

v3.0.5

• Chore release; upgraded chalk dependency in package.json to 2.2, as 2.2 appears to be a breaking changes release. - thanks @lmk123 for reporting