Releases: AviVahl/ts-tools
Releases · AviVahl/ts-tools
@ts-tools/[email protected]
- FIX: auto pick
"es2019"
(instead of"es2020"
) for Node 10+. fixes compatibility with??
syntax when used on ts3.8+.
@ts-tools/[email protected]
- upgrade to
[email protected]
.
@ts-tools/[email protected]
- FIX: corrects broken source maps when
tsconfig.json
specifiesoutDir
/outFile
.
@ts-tools/[email protected]
- upgrade to
commander@4
.
@ts-tools/[email protected]
- FIX: refactor path handling to reuse work and improve win32 compatibility.
@ts-tools/[email protected]
- Feature: lookup
tsconfig.json
and allow customizing it.
@ts-tools/[email protected]
- removed type checking. makes less sense for on-the-fly transpilation flows. using
ts.transpileModule
instead. - removed custom (via transformation)
"paths"
support. usetsconfig-paths
instead. - removed custom (
raw-loader
like).d.ts
import handing. - uses persistent dist caching (second run is really snappy).
- source maps no longer retain a ton of memory. they are extracted from cache upon need.
- simplified code-base. package now has single registration point (
/r
). - simple programmatic API to create custom extension (e.g. custom compiler options).
- no
tsconfig.json
loading yet. - single dependency left (
source-map-support
). - better windows support. canonical path is used where appropriate.
- took two steps back, one step forward.
@ts-tools/[email protected]
- accepts a function for customizing
configName
per directory (used for lookup).
@ts-tools/[email protected]
- protect against double registration when used with linked projects.
@ts-tools/[email protected]
- FIX: correct
getFileSystemEntries
whencustomFs
is used.