chore: use local TypeScript with dtslint #4712
Merged
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:
This PR reconfigures dtslint to use the locally-installed version of TypeScript - i.e. the version with which RxJS is built.
The command must be passed an absolute path to the directory that contains
typescript.js
as said path is passed torequire
in two files within the dtslint implementation that reside in different directories - so each has a different relative path the the locally-installed TypeScript. To account for this, dtslint is now invoked viaspec-dtslint/script.js
.This PR also restores numerous tests that had to be commented out due to the different behaviour of
typescript@next
.Oh, and I changedNever mind. It seems the CI build depends upon all that stuff happening after anprepublish
toprepublishOnly
as I was tired of having the build and tests run whenever I did annpm ci
. Now, that stuff will only run before an actual publish.npm install
. 😒Related issue (if exists): #4705