NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4901 most downloaded on npm
Resole and parse `tsconfig.json`, replicating to TypeScript's behaviour
Last release 9 years ago
no release in 18 months
Release timing varies
gaps range from 8 days to 8 months
Most releases are documented
notes for 21 of 24 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
24 releases · first in 2015
Support TypeScript package discovery and use NPM @types
Changed
@typesRemove buggy json-parse dependency in favour of native JSON.parse
Changed
json-parse dependency in favour of native JSON.parsePromiseReturn an empty files array when no tsconfig.json file is detected (see https://github.com/TypeStrong/ts-node/issues/157)
One column per quarter.
Changed
tsconfig.json file is detected (see https://github.com/TypeStrong/ts-node/issues/157)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
Fixed
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 achieveMark config option of result as non-optional for TypeScript (2.0 would make working with this a lot more seamless, instead of having un-assignable voi
Changed
config option of result as non-optional for TypeScript (2.0 would make working with this a lot more seamless, instead of having un-assignable void to optional params, etc)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 l…
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
{ path?: string, config: any } from load method, instead of just the tsconfig.json content without knowing where it come fromDO NOT UPGRADE IF YOU RELY ON `filesGlob` 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
tsc without the bugs that come with it (E.g. normalizeSlashes, etc.)
resolve methods now take two arguments, the cwd and an optional path (a la --project in tsc)Resolve directly to file when it exists - matches typescript@next
Changed
typescript@nextStrip JSON comments before parsing
Changed
typings field from package.jsonDistribute with typings.json on NPM
Changed
typings.json on NPMfilterDefinitions Remove non-.d.ts files from output
filterDefinitions Remove non-.d.ts files from outputresolvePaths Disable resolves files from tsconfig by defaultSet follow: true on glob options to follow symlinks
Changed
follow: true on glob options to follow symlinksAsync functions now uses promises, instead of callbacks
Changed
Fixed
globby to properly support an array over custom brace logictsconfig.json filesUses glob internally by concatenating and parsing the filesGlob option
Changed
glob internally by concatenating and parsing the filesGlob optionUsing exclude speed is improved by not traversing into the directories
Fixed
exclude speed is improved by not traversing into the directoriesFrom https://github.com/TypeStrong/tsconfig/pull/6
From https://github.com/TypeStrong/tsconfig/pull/6
npm test) work on windowsTypeScript typings should just be a module definition
Fixed
typings should just be a module definitionCreate the root defintion file (since TypeScript/TSD doesn't work yet)
Added
Support for tsconfig.json "exclude"
Added
tsconfig.json "exclude"Changed
parse-json for cleaner error messagesRemoved
tsconfig.d.ts root file hack which fails in the future - this will be solved by TSDIf resolve(Sync) fails to find tsconfig.json, it will return undefined. Load will continue throwing an error.
If resolve(Sync) fails to find tsconfig.json, it will return undefined. Load will continue throwing an error.
Changed
resolve/resolveSync will return undefined instead of throwingNew, stable API with no side effects for resolve, parsing and sanitizing tsconfig.json.
New, stable API with no side effects for resolve, parsing and sanitizing tsconfig.json.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →