Remove warning on missing baseUrl, which tsconfig-paths ^4.0.0 doesn't require anymore #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
description
motivation & context
fixes #99 (& fixes #59 - which seems a duplicated of the former)
... which follows from tsconfig-paths PR #208 which makes tsconfig-paths tolerate empty/ non-existing baseUrl's,
... which is consistent with TypeScript >=4.1 behavior
... on which frameworks (like next.js) and newer projects are starting to rely
how this was tested