Shebang line should not be passed to rules as a comment
See original GitHub issueCurrently, the shebang is being reported as a LineComment
to the rule engine, with the node value having dropped the #
so that it appears as !/usr/bin/env node
.
It would be preferable to either drop it from the program altogether, make a new node type such as Shebang
, or pass the empty string as the node value.
Issue Analytics
- State:
- Created 9 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Effects of comment (#) lines before and/or after the ...
Any line started with (#) except the shebang(#!) is treated as a comment in shell script. what is meaning of #!/bin/sh ? Its...
Read more >Shebang (Unix)
The shebang line is usually ignored by the interpreter, because the "#" character is a comment marker in many scripting languages; some language ......
Read more >Shebang line with `#!/usr/bin/env command --argument ...
Looks like this is because Linux (unlike BSD) only passes a single argument to the shebang command (in this case env).
Read more >Node.js shebang - Alex Ewerlöf
Node.js will happily ignore this as a comment only if it is the very first line of the file (it won't work even...
Read more >How to Use the Shebang in Bash and Python
Because it begins with the # symbol, the interpreter does not process the line containing the Shebang. When a Linux system executes a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Dzenly What you are describing is likely not related to this issue. Please open a new issue and please fill out this template (hopefully will be pre-rendered into the new issue form). There are a lot of pieces of information that we need, which you aren’t providing here. Again, this should be further discussed in a new issue, not this issue. Thanks!
I am about --fix option. My webstorm is setup for eslint --fix on file save and now I can not use webstorm for this file. Ok, I will think about advice to open a new issue.