-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Detect whether Grunt has run once #1600
Comments
This is because |
Thanks for reply! Yes, I know that it launches new process, but |
Just a reminder why |
Feel free to submit an rfc if you have an idea for a better API you would like to implement. I'm not sure what your use case is. Re: gruntjs/grunt-contrib-watch#510 sometimes an issue is really just a misunderstanding. Glancing at that issue, it looks like they are misunderstanding what I use |
I wonder, is there any way to detect when Grunt has run once?
In docs said that Grunt supports adding events, but doesn't emit any events itself. That's quite unfortunate, since it could help this issue.
Just to be more clear, I need to start another emitter, but it should happen only once, during init of Grunt. Right now any edits will invoke Grunt again via
grunt-contrib-watch
, thus reinitializing emitter too.I know that I can store value that it already had run once somewhere else in cache, but it would be much better to avoid disk operations. And right now there seems to be no way to store any persistent data in-memory.
The text was updated successfully, but these errors were encountered: