Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.3.0
->9.2.6
Release Notes
TypeStrong/ts-loader
v9.2.6
Compare Source
v9.2.5
Compare Source
v9.2.4
Compare Source
v9.2.3
Compare Source
v9.2.2
Compare Source
v9.2.1
Compare Source
v9.2.0
Compare Source
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
v9.0.2
Compare Source
v9.0.1
Compare Source
v9.0.0
Compare Source
Breaking changes:
Changes:
v8.3.0
Compare Source
v8.2.0
Compare Source
v8.1.0
Compare Source
v8.0.18
Compare Source
v8.0.17
Compare Source
v8.0.16
Compare Source
v8.0.15
Compare Source
v8.0.14
Compare Source
chalk
,loader-utils
, andsemver
to latest stable versions - thanks Avi Vahlv8.0.13
Compare Source
v8.0.12
Compare Source
v8.0.11
Compare Source
v8.0.10
Compare Source
v8.0.9
Compare Source
v8.0.8
Compare Source
v8.0.7
Compare Source
v8.0.6
Compare Source
v8.0.5
Compare Source
v8.0.4
Compare Source
v8.0.3
Compare Source
appendTsSuffixTo
andappendTsxSuffixTo
together - thanks @meowtecv8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
ts-loader
now supports TypeScript 3.6 and greater BREAKING CHANGEv7.0.5
Compare Source
v7.0.4
Compare Source
v7.0.3
Compare Source
v7.0.2
Compare Source
v7.0.1
Compare Source
v7.0.0
Compare Source
ts-loader
no longer supports Node 8 BREAKING CHANGEv6.2.2
Compare Source
webpack.config.ts
files - thanks @vladimiry!v6.2.1
Compare Source
v6.2.0
Compare Source
v6.1.2
Compare Source
v6.1.1
Compare Source
v6.1.0
Compare Source
v6.0.4
Compare Source
v6.0.3
Compare Source
v6.0.2
Compare Source
v6.0.1
Compare Source
v6.0.0
Compare Source
v5.4.5
Compare Source
v5.4.4
Compare Source
v5.4.3
Compare Source
v5.3.3
Compare Source
v5.3.2
Compare Source
v5.3.1
Compare Source
v5.3.0
Compare Source
resolveNodeModule
option - thanks @arcanis!v5.2.2
Compare Source
v5.2.1
Compare Source
v5.2.0
Compare Source
projectReferences
- thanks @andrewbranch!v5.1.1
Compare Source
v5.1.0
Compare Source
experimentalFileCaching
- thanks @timocov!v5.0.0
Compare Source
v4.5.0
Compare Source
v4.4.2
Compare Source
v4.4.1
Compare Source
v4.4.0
Compare Source
v4.3.1
Compare Source
Please note, this bug fix requires that vue-loader users still using v14 should either upgrade to v15 or explicitly pass the same ts-loader options via v14's loaders option. See more details here
v4.3.0
Compare Source
allowTsInNodeModules
option for importing .ts files from node_modules - thanks @aelawson!v4.2.0
Compare Source
v4.1.0
Compare Source
experimentalWatchApi
(#746) - thanks @sheetalkamat and @MLoughry!getCustomTransformers
support path string for a module - thanks @vagusX and @s-panferov (upon whose work this is based I believe)v4.0.1
Compare Source
v4.0.0
Compare Source
entryFileCannotBeJs
removed' BREAKING CHANGEv3.5.0
Compare Source
v3.4.0
Compare Source
v3.3.1
Compare Source
v3.3.0
Compare Source
reportFiles
option - thanks @freeman!contextAsConfigBasePath
withcontext
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 usingcontextAsConfigBasePath
- thanks @christiantinauer!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
Compare Source
contextAsConfigBasePath
- thanks @christiantinauerv3.1.1
Compare Source
v3.1.0
Compare Source
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 @johnnyreillyv3.0.5
Compare Source
package.json
to 2.2, as 2.2 appears to be a breaking changes release. - thanks @lmk123 for reportingv3.0.4
Compare Source
v3.0.3
Compare Source
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.v3.0.2
Compare Source
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.