This probably boils down to #2165, if the solution is to not cache locally resolved files at all. This is really a problem if you have multiple examples all containing their own node_modules/. it looks like installing a package with file: puts a module in the cache containing node_modules/ and other stuff. Again my colleagues don't have as much problems installing as I do. I don't know if my hardware is broken handling a lot of small files or something like that or if this is related at all. I have a lot of problems installing which has a lot of small files which seem to be troublesome for other people as well ( google/material-design-icons#518). We also have some relative files with path: protocol in our package.json. However my colleagues don't suffer from this problem, so I don't think the custom private registry is the problem (and fetching packages is already finished anyway). I use the official registry as well as a custom private registry for certain scoped packages. I currently try it with a clean cache and nightly (v0.22.0-20170226.1626). yarn sometimes tries to link around 600.000 files in small projects. ![]() Not related to windows.Īnd it seems my setup is way slower than others in this thread. I can confirm that it is very slow on Mac 10.12.3, too. ![]() "force-case-sensitivity-webpack-plugin": "0.1.1", "babel-plugin-transform-object-rest-spread": "6.8.0", ![]() "babel-plugin-transform-class-properties": "6.9.1",
0 Comments
Leave a Reply. |