Releases: TypeStrong/tsconfig
Releases · TypeStrong/tsconfig
@types
ES2015
Changed
- Remove buggy
json-parse
dependency in favour of nativeJSON.parse
- Use native
Promise
Empty Files On No Resolve
Changed
- Return an empty files array when no
tsconfig.json
file is detected (see TypeStrong/ts-node#157)
Prefer Resolve Over Join
Fixed
- Use
path.resolve
for loading configuration in case of specifying an absolute path -path.join
would just join them together which is probably not what the user wanted to achieve
Mark Load Config As Non-Optional
Changed
- Mark
config
option of result as non-optional for TypeScript (2.0 would make working with this a lot more seamless, instead of having un-assignablevoid
to optional params, etc)
Load Result
Two major releases in a day, that's when you should probably take a break. This breaking change returns the path to the configuration when using the load
method. This is super useful because TypeScript will need it to actually read the configuration.
Changed
- Output
{ path?: string, config: any }
fromload
method, instead of just thetsconfig.json
content without knowing where it come from
Mirror TypeScript Behaviour
DO NOT UPGRADE IF YOU RELY ON filesGlob
BEHAVIOUR
This release is prepared to projects that wish to use/mirror tsc
behaviour and is more forward-facing - removing custom filesGlob
expansion and option mutation for the official 2.0 includes
option
Changed
- Simply the module API surface and dependencies by changing it to be a direct API replication of
tsc
without the bugs that come with it (E.g.normalizeSlashes
, etc.)resolve
methods now take two arguments, thecwd
and an optionalpath
(a la--project
intsc
)- Removed automatic configuration expansion and mutation - now directly returns the parsed configuration file
Read File
Changed
- Resolve directly to file when it exists - matches
typescript@next
Strip JSON Comments
Changed
- Strip JSON comments before parsing
- Remove
typings
field frompackage.json
Typings
Changed
- Distribute with
typings.json
on NPM