Yarn needs to use .npmignore file when installing from repo

[danielkcz]

Do you want to request a feature or report a bug?
Feature (I would like think of it as a bug too)

What is the current behavior?
Trying to install three.js module from repository instead of registry yields 303MB folder in size. Installing same thing with NPM and resulting folder is just 11MB

If the current behavior is a bug, please provide the steps to reproduce.
yarn init
yarn add github:mrdoob/three.js

What is the expected behavior?
The .npmignore file should be used and actually remove files that conforms to globs there. Not sure if it's possible to actually avoid unpacking those files in first place. That would certainly improve performance much more.

Reason why to install package from repository is because of custom forks.

Please mention your node.js, yarn and operating system version.
Node 6.9.1, Yarn 0.17.7, Windows 10 x64

[Daniel15]

module from repository instead of registry

What's the use case for this? Is it just to install a development version?

[danielkcz]

@Daniel15 Already said that in original post...

Reason why to install package from repository is because of custom forks.

Or actually any private modules as well.

[Daniel15]

Ahhh, so sorry @FredyC, I totally missed that part of your post! For custom forks of open source libraries, one option is to publish them to npm as a namespaced/scoped package (like @fredyc/foo), which should behave better than installing it directly from the repo (in theory).

In any case, this definitely sounds like an improvement we should make :)

[danielkcz]

I personally dislike polluting npm registry more than is needed, even with something like scoped packages. Doesn't feel right, but I guess it's possible workaround for now.

Either way it wont work for private modules anyway.

[domakas]

This is a huge deal-breaker for us, would be nice to solve it as soon as possible.

Any ideas what strategy could be used for this? I might be interested in solving this issue myself, however, I don't have any other ideas as just checking out full repo and deleting files which match .npmignore/.yarnignore

[bbrzoska]

Same problem occurs when you try to install from a local directory #685.

[rmm5t]

Just ran into this problem myself. I was really surprised by the behavior, and it's causing the associated directory in our node_modules to sit at 12MB when using yarn install, but npm install correctly ignores the files from the repo leaving the directory at just 32KB.

We have a private module and share it via a git repository.

It's important for us to keep our node_modules small, because they are packaged up as part of our deployments to AWS Lambda. The larger the package deployment, the slower our cold-starts on Lambda.

$ node --version
v6.10.0

$ yarn --version
0.27.5

[mblackritter]

Hmmm, any news on that? I was just surprised when adding a dependency to a local modules via "[package-name]": "file:../[path]" and found ~300 MB in the imported ~10kb module after yarn install.

[stantoncbradley]

this hurts. importing a lib from git repo to react native. yarn not ignoring .babelrc so getting transform errors when compiling react native app because I don't have the babel transform plugins installed for my app

[HaykoKoryun]

Any update on this? It might not be a big deal when developing projects, but it becomes a sticking point when trying to use yarn in production.

[andreialecu]

Also got hit by this while trying to use webpack with the angular2+ AOT compiler to compile a project that references a private library which has .ts files along the transpiled .js files.

Due to configuration requirements, webpack will default to finding and using the .ts files, but the typescript compiler will refuse to compile anything from node_modules resulting in a failed build.

Using .npmignore to ignore .ts files would've solved this.

(Workaround was to reorganize the entire project to store the compiled .js files in a separate directory, so that the .ts files weren't siblings to them.)