We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
By default, npm puts a newline at the end of package-lock.json but when npm-force-resolutions rewrites the file, it does not include a final newline.
This is not a major problem but it does trigger my linters since it's unexpected.
The text was updated successfully, but these errors were encountered:
Tabs are also converted to spaces, making diffs difficult to read if the package-lock.json file was not already using spaces.
Sorry, something went wrong.
No branches or pull requests
By default, npm puts a newline at the end of package-lock.json but when npm-force-resolutions rewrites the file, it does not include a final newline.
This is not a major problem but it does trigger my linters since it's unexpected.
The text was updated successfully, but these errors were encountered: