-
Notifications
You must be signed in to change notification settings - Fork 7
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
.gitignore becomes .npmignore on run #64
Comments
This issue does not appear to happen when running the |
Similar issue that was seen in this thread: npm/npm#1862 |
if there's a empty .npmignore, .gitignore would not be touched |
@abhishekr700 after looking at the above issue, I'm not sure that's the case (also, I don't think we would actually want an empty one, rather something that is a copy of our existing gitignore). Where did you see that was the case (or do you have an example running where that is the case)? |
I read something similar here npm/npm#3763 |
the latter comments (and the ones on the issue @chtinahow linked) seem to indicate that regardless of what files you have, all |
Summary
For some reason, the .gitignore file becomes an .npmignore file on running tram-one-express... Not sure why, or when this regression happened.
This could be a documented feature of npm / node. Requires investigation.
The text was updated successfully, but these errors were encountered: