-
Notifications
You must be signed in to change notification settings - Fork 944
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
Suggestion: --skipIgnoreFile argument to silent error "Could not read .foreverignore file" #1024
Comments
ww9
changed the title
Suggestion: --noconfig argument to silent error "Could not read .foreverignore file"
Suggestion: --skipIgnoreFile argument to silent error "Could not read .foreverignore file"
Mar 14, 2019
Nevermind, nodemon works for my usecase out of the box so I'm switching to that. |
Pull request would be awesome, though, if you could push the code you wrote :) |
Sure why not. Let me reopen this. Will close once PR is merged in both repos. |
This was referenced Mar 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I couldn't find an argument to silent the error:
Could not read .foreverignore file
.I'm using forever to restart a Node.js script whenever I press CTRL+S in the editor. This gives me quick feedback and it's awesome. However, I don't need the ignore file and I'd love to silent that error.
I've read #590 and it seems that this is considered a bug as @indexzero wrote:
Since this has been the default behavior for so long, I'm afraid that simply silencing this error by default would cause more harm than good for developers and projects that expect it.
Perhaps forever could implement a --skipIgnoreFile parameter?
Thoughts?
The text was updated successfully, but these errors were encountered: