An in-range update of tslint is breaking the build 🚨
Created by: greenkeeper[bot]
tslint just got published.
Version 4.2.0 ofBranch |
Build failing |
---|---|
Dependency | tslint |
Current Version | 4.1.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this
Status Details
Release Notes
4.2.0- [new-rule]
no-string-throw
(#1878) - [new-rule]
no-empty-interface
(#1889) - [new-rule]
interface-over-type-literal
(#1890) - [new-rule]
callable-types
(#1891) - [new-rule]
no-void-expression
(#1903) - [new-rule-option]
ban-single-arg-parens
added toarrow-parens
(#1893) - [bugfix]
prefer-const
handles destructuring arrays (#1894), destructuring objects (#1906), and forward references (#1908) - [bugfix] Don't error for misplaced braces for 'else' in
one-line
rule (#1866) - [bugfix]
no-shadowed-variable
now identifies shadowedfor
iterator (#1816) - [bugfix]
object-literal-key-quotes
now includes function names (#1874) - [bugfix] error when EOF comes after
disable-next-line
comment (#1902)
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot