-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
grunt-simple-watch is not maintained #182
Comments
You could probably use https://github.com/e-feit/grunt-simple-watch-legacy? That said, Grunt itself is barely maintained, based on https://github.com/gruntjs/grunt/graphs/contributors... perhaps it's time to stop using Grunt? |
After looking into this, we decide to replace simple-watch with chokidar. This issue is fixed by #185. Marking as closed. |
Can anyone tell about how to use forked repository?
|
I have a project that ran into this issue: unbalanced/grunt-simple-watch#13. It seems that when using lodash versions > 4.0, the syntax in grunt-simple-watch breaks. The fix is simple, and available in that pull request... which has been sitting there for 2 years un-merged. This is the repo that the npm package uses.
Now I don't understand why this project in particular ended up with lodash 4.0+, while most other projects I have using gesso seem to end up with 0.9.2 installed. I believe 0.9.2 is normally used because gesso uses 4.5.0, which declares lodash 0.9.2 as a dependency. Previous versions of grunt-simple-watch do not specify any dependency on a version of lodash, and the project doesn't explicitly set it as a dependency either. Although multiple web-starter generators declare dependencies on lodash > 4.0.
The maintainer of grunt-simple-watch doesn't appear to have been active on GitHub Suffice to say, if we aren't running into this issue already, we will eventually. There does seem to be a number of forks of grunt-simple-watch available that include this patch. I'm not sure on the best solution here, I'm just raising it as an issue. I suppose we don't need to do anything here, since we should be taken care of by the grunt version, but writing this issue up was a rubber duck moment for me, and I didn't want it to go to waste. So in the spirit of future-proofing gesso, We could:
The text was updated successfully, but these errors were encountered: