-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: No Export in a Shebang file #331
Comments
We switched to it in eg. Try that module out and if it isn't fixed there, then open a new issue in that project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I feel like this rule would help a lot of new node users that love making CLI & bin application with it (like me😊).
I have a large CLI app with functions imported and exported from other files and found out (after too much debugging) that exporting a function from a file that has a shebang declaration the top of it (like
#! /usr/bin/env node
) gives a lot of trouble in execution.I would suggest an optional rule that looks for
export
in a shebang file and alert about it.The text was updated successfully, but these errors were encountered: