You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that while coveralls is used in Travis CI it would produce no extra output on a passing build (see GH-251 for passing "Node.js" build). I can think of a couple possible solutions:
completely remove coveralls
update coveralls to resolve npm audit issues then configure a reporter or connect to coveralls.io
P.S. What should we do about travis-cov devDep? Can we remove it? (travis-cov is now removed)
The text was updated successfully, but these errors were encountered:
So I think we want to try to solve the conflicts, looking back through the project, it indeed was intended to produce security coverage scans for SonarCloud. I'll put this on a list of things to look at, perhaps it is indeed extraneous. Thanks!
I noticed that while
coveralls
is used in Travis CI it would produce no extra output on a passing build (see GH-251 for passing "Node.js" build). I can think of a couple possible solutions:npm audit
issues then configure a reporter or connect to coveralls.ioP.S.
What should we do about(travis-cov
devDep? Can we remove it?travis-cov
is now removed)The text was updated successfully, but these errors were encountered: