Closed marcysutton closed 6 years ago
Looks like this has been fixed on master
, just not tagged or deployed to NPM. I've run the tests locally and they all pass so (superficially) it looks ready to go.
@shama Would you be able to take a look at this? (Pinging since I see you did the last tags and recently fixed grunt-legacy-log similarly) Let me know if I can help.
came in here to report the same issue. it will make a huge difference if you could find time and deploy current master to npm
Sorry for the delay, a new version of grunt-contrib-watch@1.0.1
was published with the lodash
dependency updated. Thanks!
There is a known security vulnerability in lodash@3x: https://hackerone.com/reports/310443
The severity is low, however grunt-contrib-watch should be updated to the latest lodash version to reduce risk.