New rule: unicode-bom #538

Closed
feross opened this Issue Jun 2, 2016 · 5 comments

Projects

None yet

3 participants

@feross
Owner
feross commented Jun 2, 2016

http://eslint.org/docs/rules/unicode-bom

This was previously covered by no-irregular-whitespace but BOM characters at the beginning of files are now stripped by eslint, so adding this rule just gets us the old behavior again.

@dougwilson

What is the suggested value for the rule? "never" I assume?

@feross
Owner
feross commented Jun 2, 2016

Yep. Setting it to "never" would match the old behavior of the no-irregular-whitespace rule.

@yoshuawuyts
Collaborator

I'm only like half-understanding this rule; not spotting any way it affects anything I've ever done with JS so 👍 I guess

@feross
Owner
feross commented Jun 2, 2016

@yoshuawuyts See #283 for some more context, if you're interested.

@feross feross modified the milestone: v8 Jul 12, 2016
@feross feross referenced this issue Jul 12, 2016
Closed

Release proposal: standard v8 #564

16 of 16 tasks complete
@feross feross added a commit to feross/eslint-config-standard that closed this issue Jul 12, 2016
@feross Disallow the Unicode Byte Order Mark (BOM) (unicode-bom) e5e37a9
@feross
Owner
feross commented Jul 12, 2016

This rule will be included in standard v8

@saadq saadq referenced this issue in nodejs/nodejs.org Aug 25, 2016
Merged

Update dependencies #873

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment