Skip to content
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

Conversation

bmacnaughton
Copy link
Contributor

It wasn't clear that files not included in the "files" field are excluded if the field is present.

It wasn't clear that files not included in the "files" field are excluded.
@fahrradflucht
Copy link

Just out of curiosity: I don't understand what else the text could have meant before your change. Could you elaborate?

@iarna
Copy link
Contributor

iarna commented Sep 14, 2017

I think what they're trying to communicate is that if you use files it overrides a top level .npmignore or .gitignore?

Copy link
Contributor

@zkat zkat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds about right, to me. Hopefully it'll help clarify things to people.

@zkat zkat changed the base branch from master to release-next March 6, 2018 22:45
@zkat zkat requested a review from a team as a code owner March 8, 2018 20:59
@zkat zkat merged this pull request into npm:release-next Mar 8, 2018
zkat pushed a commit that referenced this pull request Mar 8, 2018
It wasn't clear that files not included in the "files" field are excluded.

PR-URL: #18407
Credit: @bmacnaughton
Reviewed-By: @zkat
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants