Prune root tsconfig and dependency updates

What's Changed

Remove references and paths that are already in some tsconfig's further down the file structure tree. So we only have things in the root that haven't referenced somewhere else.

• including some vulnerability fixes
• migrating from jest to vitest

BREAKING CHANGE: dropping support for older node.js versions before 22.13.0

Full Changelog: 4.0.0...5.0.0

Basic support for jsconfig.json

What's Changed

• feat!: adding basic support for jsconfig.json files by @MKruschke in #52

BREAKING_CHANGE: this might come in with some site effects if you had already jsconig.json files in your repo and now the will be picked up automatically

Full Changelog: 3.6.2...4.0.0

Avoid adding an empty compilerOptions to the tsconfigs

What's Changed

• fix: avoid adding an empty compilerOptions object by @MKruschke in #50

Full Changelog: 3.6.1...3.6.2

remove unused dependencies

What's Changed

• chore: remove unused dependencies by @jergason in #47

Full Changelog: 3.6.0...3.6.1

Ignore Paths mappings for packages

You can now configure (via the config yaml) which packages shouldn't be mapped under compiler options paths. To have a path mapping could be an issue for packages that rely on exports for different environments and a fallback to index.ts isn't working.

Improve paths resolution by using the rootDir from tsconfig

What's Changed

• feat: use rootDir for paths resolution
• fix: fix for applying paths to the root tsconfig

#45
Full Changelog: 3.4.0...3.5.0

3.4.0

What's Changed

• feat: support projects without root tsconfig and add new strict mode #44

Full Changelog: 3.3.0...3.4.0

Support different configuration files for different usecases

3.3.0

feat: support different configuration files for different usecases (#39)

Create path mappings under compilerOptions for non-ts packages

Path mappings for packages without tsconfig will be added to the root tsconfig to leverage your IDE resolution support more (during your migration phase). Please also note that with that release the --check option also respects compilerOptions.paths differences but only in combination with --createPathMappings.

Create path mappings under compilerOptions

It's now also possible to write path mappings under compilerOptions. This is beneficial in combination with your IDE to resolve usages better.