get-tsconfig

get-tsconfig copied to clipboard

This package does not correctly resolve paths

1

### Problem This package says that it resolves extends, and is intended to work how the TypeScript compiler / language services do in figuring out your current configuration. But it...

matthew-dean

feat: add `fallback` option to avoid meaningless result.

7

https://github.com/privatenumber/get-tsconfig/issues/65

emosheeep

Undeclaring paths alias causes a incorrect match result

2

### Problem I don't declare a path alias link '@libs/*', and when I use a matcher created by createPathsMatcher, it results ``` @libs/constants → /cwd/@libs/constants ``` It doesn't make sense...

emosheeep

- Rename `parseTsconfig` -> `readTsconfig` - If given a file path to `getTsconfig`, check if the found tsconfig's `includes` matches the file path - Move `createPathsMatcher` out to a different...

privatenumber

feat: TypeScript resolver

1

privatenumber

Align properties of `TsConfigJsonResolved` with TypeScript's `ParsedCommandLine`

3

See also [`ParsedCommandLine`](https://github.com/microsoft/TypeScript/blob/fd3a84c3f0c80cb201c47399a055625f919a9b91/lib/typescriptServices.d.ts#L3168-L3178) https://github.com/microsoft/TypeScript/blob/fd3a84c3f0c80cb201c47399a055625f919a9b91/lib/typescriptServices.d.ts#L3168-L3178 --- I'd like to replace parsing `tsconfig.json` from TypeScript to `get-config` more seamlessly. It would be a BREAKING CHANGE.

JounQin

feat: TypeScript resolver

6

Reproduction detail #19

JounQin

This PR adds a test demonstrating and documenting the difference between include paths handling in tsc (no path normalization) and get-tsconfig (does path normalization), as described in #73.

inga-lovinde