This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Fix CI: no-implicit-dependencies test failure; typescript@next failure #4019
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.
Fixes build status:
Failing tests on
master
caused by consequent merges of #3979 and #3875.whitelist-with-dev
with option"dev"
: the rule looks at bothdev
andpeer
dependencies, thus allowingtypescript
package to be used.As it turned out, there is another PR fixing this (#4011)
Failing
testNext
step caused by removedunescapeIdentifier()
(microsoft/TypeScript#25333)Changes overview:
noStringLiteralRule.ts
tsutils
(fixed in 2.27.2, version bumped)tsutils@2.27.2
relies on typescript@2.9.x (version bumped)noUnsafeAnyRule.ts
due to updated typings