This repository was archived by the owner on Feb 12, 2024. It is now read-only.
Fix linter errors #918
Closed
Fix linter errors #918
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Use `safe-buffer` everywhere
Closed
Contributor
Author
|
Closing because this is not relevant for now.. can reopen later |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
safe-buffereverywhereI previously had issues with running
npm run lint, which required me to additional eslint plugins. I can no longer reproduce that anymore. Strange..e: Whoops, I happened to be using eslint-config-standard v10 instead of 7.. Version 7 does not yet check use of
new Buffer().. So this pr wont be relevant until aegir@next which will use a later version