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

Yarn keeps all project files ignoring what is defined on package.json's "files" prop #5309

Closed
melloc01 opened this issue Feb 2, 2018 · 1 comment
Assignees
Labels

Comments

@melloc01
Copy link

melloc01 commented Feb 2, 2018

Do you want to request a feature or report a bug?
Report a bug.

What is the current behavior?
yarn keeps all the project files when using a git project as dependency. npm keeps only the files on the "files" config prop.

If the current behavior is a bug, please provide the steps to reproduce.
1 - Use this repo as dependency of a project.
2 - Install via yarn
3 - Install via npm

contents on node_modules will differ.

What is the expected behavior?
As descripted on the docs

""files" field is an array of file patterns that describes the entries to be included when your package is installed as a dependency."

So it is expected to only have the files listed on the config to be present.

Please mention your node.js, yarn and operating system version.

  • Deepin Linux@15.5
  • yarn@1.3.2
  • npm@5.6.0
@ghost ghost assigned rally25rs Feb 2, 2018
@ghost ghost added the triaged label Feb 2, 2018
@rally25rs
Copy link
Contributor

duplicate #2822

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants