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
{{ message }}
This repository has been archived by the owner on Dec 29, 2020. It is now read-only.
We're currently using grunt-jscs-checker in one of our projects, and recently, there was an update to node-jscs in 1.4.4 that caused everything to break (jscs-dev/node-jscs#376).
Since your version dependancy was set to ~1.4.3 (which really means 1.4.X), it was causing us to download the broken 1.4.4. I would suggest being explicit about which version to match rather then using ~.
Let me know if you think this is a good change :)
The text was updated successfully, but these errors were encountered:
It's not about panicking - this is obviously a special case where jscs was completely broken. But what if there was a less obvious bug that was introduced in jscs 1.4.5? I don't see why you wouldn't just want to lock the version explicitly to avoid issues arising in the future.
Hi!
We're currently using grunt-jscs-checker in one of our projects, and recently, there was an update to node-jscs in 1.4.4 that caused everything to break (jscs-dev/node-jscs#376).
Since your version dependancy was set to ~1.4.3 (which really means 1.4.X), it was causing us to download the broken 1.4.4. I would suggest being explicit about which version to match rather then using ~.
Let me know if you think this is a good change :)
The text was updated successfully, but these errors were encountered: