-
Notifications
You must be signed in to change notification settings - Fork 342
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
Add an option to write a final newline #115
Comments
What is the usecase for not wanting a final EOL? |
Projects may have a .editorconfig with An other reason is a library produce json files with no final EOL. When you start using node-jsonfile module internally, you don't want to change the behavior or your API. |
I don't really get the point of this since final EOLs are a strong Unix convention; but I would consider it if someone did a PR. |
@RyanZim i would like to pick this up |
@asingh04 go for it. |
The PR for this feature: |
The final newline to the files produced should be optional.
The text was updated successfully, but these errors were encountered: