Closed greenkeeper[bot] closed 6 years ago
Update to this version instead π
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.
The new version differs by 11 commits.
81d02db
Merge pull request #658 from johnnyreilly/master
2aaba6e
Deprecate entryFileCannotBeJs
173bd4c
Change getCurrentDirectory behaviour for TypeScript 2.3 and below
a91a8b4
make nodeResolutionAllowJs run in 2.4+ only
a2b613a
try strategy approach splitting 2.4 and above and 2.3 and below behaviour
e576c92
check old strategy behaviour
cb303f5
drop resolveTypeReferenceDirectives for a moment
9f4cc4f
Add back support for TypeScript < 2.4
f832bb6
Fix allowJs import @types issue
a504b11
added nodeResolutionAllowJs test (will fail initially)
b182a65
republish as 3.0.2
See the full diff
Update to this version instead π
The new version differs by 19 commits.
bb0b09d
Prepare for 3.0.4 release
2e2f29a
Add hot example
cb33f9d
Merge pull request #662 from johnnyreilly/master
f7e500c
Upgrade examples to ts-loader 3 and webpack 3 (and react 16 where applicable)
8972715
removed webpack 1 example
93dd166
Made happypack a dependency of the test rather than ts-loader
a2b9cc3
Added licenses to package.jsons
239bf5a
upgrade chalk and webpack
8bad811
ignore debug.log files
ac273ea
delete debug.log
ea39a87
Removed typings usage
107fb8f
instance still seems to be flaky
e0c56aa
fx-extra upgrade
a5aa51b
fix tsconfigInvalidFile
ef1f8d6
Fix instance test
There are 19 commits in total.
See the full diff
Update to this version instead π
onlyCompileBundledFiles
option which modifies behaviour to load only those files that are actually bundled by webpack #267 - thanks @maier49!package.json
to 2.3, as 2.3 is another breaking changes release (from a TypeScript perspective)., see here for context - thanks @johnnyreillyThe new version differs by 17 commits.
605727d
Prepare for 3.1.0 release
d946cb6
Update CHANGELOG.md
32fa70c
Merge pull request #671 from maier49/compile-bundled-files-and-typing-files
705741e
Resolve PR feedback
73af60c
Fix indentation
4ad8846
Add option to compile bundled files and .d.ts files only
cc1c037
Merge pull request #670 from ORESoftware/patch-1
9136ec4
demonstrated usability with watchers such as webpack -w
3fcb7e9
Merge pull request #669 from johnnyreilly/master
e50d5cd
Fix chalk 2.3 incompatibility
d3cb684
Fix HMR examples
433c7d8
rename hot to core-js
c19c945
simplify hot
e620352
updated deps
300da75
Add react-hot-boilerplate based on @gaearon's example
There are 17 commits in total.
See the full diff
Update to this version instead π
Fix error importing buildt ts files with allowJs (#667) - thanks @Pajn!
The new version differs by 6 commits.
8a5de24
prepare for 3.1.1 release
59ca674
Update CHANGELOG.md
5e1b477
Merge pull request #674 from Pajn/fix-667
e78c31b
Merge pull request #675 from FLGMwt/patch-1
5e434e2
typo: s/will generated/will generate
bc926d0
Fix none-node_module imports of built ts files
See the full diff
Update to this version instead π
The new version differs by 18 commits.
e5b2f51
Prepare 3.2.0 release
ba72dfc
Merge pull request #681 from christiantinauer/master
c95bdfe
Merge pull request #673 from trodrigues/master
f37e438
Update browserMocks.js
2d09770
Add description of option "contextAsConfigBasePath" to README.
02fe053
Fixed comparison test "validateLoaderOptionNames".
4c713e0
Add execution-test for option "contextAsConfigBasePath".
ebd2bb5
Add new loader option "contextAsConfigBasePath", which when set to true, parses to tsconfig file with respect to webpack context path (https://webpack.js.org/configuration/entry-context/#context) instead of the location of the config file. So all relative paths in config file are treated relative to webpack context This makes configurations possible, where the tsconfig file is located in a npm package or elsewhere in the project structure.
88809f9
Update README with explanation
5a32a07
Update example to actually include some typed code
013bac9
Merge pull request #678 from johnnyreilly/master
0951587
regenerate output for 2.6 and add 2.6 to test matrix
512c9e6
create ts 2.6 comparison-test results
4d4b8aa
upgraded to building with ts 2.6
e4cbeb8
Merge pull request #676 from gsteacy/master
There are 18 commits in total.
See the full diff
Version 3.0.0 of ts-loader was just published.
The version 3.0.0 is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ts-loader.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donβt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v3.0.0All changes were made with this PR - thanks @johnnyreilly
entryFileIsJs
option; it can be inferred from whether theallowJs
TypeScript compiler option has been set.configFileName
support (replaced byconfigFile
) BREAKING CHANGEFAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: