Skip to content
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

Do we need field “files” in “package.json”? #25

Closed
tripu opened this issue Jul 6, 2017 · 2 comments
Closed

Do we need field “files” in “package.json”? #25

tripu opened this issue Jul 6, 2017 · 2 comments

Comments

@tripu
Copy link
Member

tripu commented Jul 6, 2017

Documentation says that that's a list of files to be included, but npm publish includes all files in the current dir, anyway (unless explicitly excluded).

So, what's the point of that list? It has to be manually maintained, eg updated every time a file is added/removed/renamed…

See #24.

@iherman
Copy link
Member

iherman commented Jul 29, 2017

@tripu I must admit I do not know. I just followed what npm seems to do and what is in the documentation...

@tripu
Copy link
Member Author

tripu commented Aug 20, 2017

Okay, I think we can remove that section. I'll do that.

@tripu tripu self-assigned this Aug 20, 2017
tripu added a commit that referenced this issue Aug 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants