Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Rule proposal: unicode-bom (byte order mark, U+FEFF)
See original GitHub issueWhen does this rule warn?
When there is a BOM in a file checked by ESLint. This has happened to me after inheriting some code. My editor (atom) doesn’t show the mark, but I see it on git diff.
Is this rule preventing an error or is it stylistic? Stylistic
Why is this rule a candidate for inclusion instead of creating a custom rule? I believe this rule is related to whitespace rules, which are in the ESLint core already.
Are you willing to create the rule yourself? Yes, though I am not sure how to, yet.
Issue Analytics
- State:
- Created 8 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
To confirm, we’ll be implementing
unicode-bomwith always/never, notno-bomwith no option, correct?If so, can someone please change the title of this issue accordingly? Thanks!
Sounds like @mysticatea is championing this rule.