Skip to content
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

Conversation

pablobirukov
Copy link
Contributor

@pablobirukov pablobirukov commented Jul 9, 2018

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 both dev and peer dependencies, thus allowing typescript package to be used.

As it turned out, there is another PR fixing this (#4011)

Failing testNext step caused by removed unescapeIdentifier() (microsoft/TypeScript#25333)

Changes overview:

  • the method was used in noStringLiteralRule.ts
  • the method was used in tsutils (fixed in 2.27.2, version bumped)
  • tsutils@2.27.2 relies on typescript@2.9.x (version bumped)
  • minor change in noUnsafeAnyRule.ts due to updated typings

@pablobirukov pablobirukov force-pushed the fix-ci-after-no-implicit-dependencies branch 2 times, most recently from 7ef96b7 to 4c4e6a0 Compare July 9, 2018 15:26
@pablobirukov pablobirukov force-pushed the fix-ci-after-no-implicit-dependencies branch from 09782f1 to cfe7e0a Compare July 9, 2018 15:35
@pablobirukov pablobirukov changed the title Fix CI, which became red after consequent merge #3979, #3875 Fix CI: no-implicit-dependencies test failure; typescript@next failure Jul 9, 2018
@reichhartd reichhartd mentioned this pull request Jul 9, 2018
4 tasks
@johnwiseheart johnwiseheart merged commit 29fbace into palantir:master Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants