This version is covered by your current version range and after updating it in your project the build failed.
snyk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 1.34.2 of snyk just got published.
This version is covered by your current version range and after updating it in your project the build failed.
snyk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/spences10/c-counter/0f38d6294b6b926bf1c39c12a086bc1f249fbf86/dependencies/npm#filter-failing-dep) - ❌ **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/spences10/c-counter/0f38d6294b6b926bf1c39c12a086bc1f249fbf86/files#filter-failing-file)Release Notes
v1.34.2<a name"1.34.2">
1.34.2 (2017-06-07)
Bug Fixes
snyk wizard
when monitoring without packageManager (d102a602)Commits
The new version differs by 1 commits.
d102a60
fix: crash in
snyk wizard
when monitoring without packageManagerSee the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: