An in-range update of @types/xml2js is breaking the build 🚨

[greenkeeper]

The devDependency @types/xml2js was updated from 0.4.4 to 0.4.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/xml2js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ codecov/project: No report found to compare against (Details).
• ❌ spmeesseman.svn-scm-ext: 3 errors / 9 warnings
• ❌ spmeesseman.svn-scm-ext (Windows CodeInssiders): 1 errors / 1 warnings
• ✅ spmeesseman.svn-scm-ext (Windows CodeCurrent): 0 errors / 1 warnings
• ✅ spmeesseman.svn-scm-ext (Windows Code26): 0 errors / 1 warnings
• ❌ spmeesseman.svn-scm-ext (Linux CodeInssiders): 1 errors / 1 warnings
• ❌ spmeesseman.svn-scm-ext (macOS CodeInssiders): 1 errors / 1 warnings
• ✅ spmeesseman.svn-scm-ext (Linux CodeCurrent): 0 errors / 1 warnings
• ✅ spmeesseman.svn-scm-ext (macOS CodeCurrent): 0 errors / 1 warnings
• ✅ spmeesseman.svn-scm-ext (Linux Code26): 0 errors / 1 warnings
• ✅ spmeesseman.svn-scm-ext (macOS Code26): 0 errors / 1 warnings

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 0.4.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.