You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a self-executable Node.js file, which starts with a Unix hashbang like #!/usr/bin/env node, and you run eslint . --fix (with flowtype/require-valid-file-annotation set to always), it inserts a // @flow comment on the top line above the hashbang, resulting in broken syntax.
In files that start with #!, this first line can never have abnything inserted before it. The actual JavaScript content effectively starts on the second line in these kind of files.
The text was updated successfully, but these errors were encountered:
If you have a self-executable Node.js file, which starts with a Unix hashbang like
#!/usr/bin/env node
, and you runeslint . --fix
(withflowtype/require-valid-file-annotation
set toalways
), it inserts a// @flow
comment on the top line above the hashbang, resulting in broken syntax.In files that start with
#!
, this first line can never have abnything inserted before it. The actual JavaScript content effectively starts on the second line in these kind of files.The text was updated successfully, but these errors were encountered: