Size of initial StockDog folder ~200 MB?

matthiku · May 6th, 2015, 06:37 AM

After "scaffolding" the StockDog app with Yeoman, -

Code:

yo angular StockDog

that folder contains ~28,000 files and more than 6000 subfolders and a total size 143 MB!

Is that normal? Or did something go wrong during that initial process? Everything seems to work, though.

Praxia · August 19th, 2015, 09:47 PM

Quote:

Originally Posted by matthiku

After "scaffolding" the StockDog app with Yeoman, -

Code:

yo angular StockDog

that folder contains ~28,000 files and more than 6000 subfolders and a total size 143 MB!

Is that normal? Or did something go wrong during that initial process? Everything seems to work, though.

I second that question! The scaffolding file size/numbers are absurd. I'm well over 100MB. I also need some insight into why?

Praxia · August 20th, 2015, 11:40 AM

I guess this is "normal" for Yeoman scaffolding files size: http://stackoverflow.com/questions/1...-and-11k-files

dougal83 · August 24th, 2015, 06:38 AM

Quote:

Originally Posted by Praxia

I guess this is "normal" for Yeoman scaffolding files size: http://stackoverflow.com/questions/1...-and-11k-files

You're right, it is normal. The node and bower modules recursively keep their own copies of their dependencies in a tree of folders. This behaviour seems to be a bone of contention within the community.

If you're using source control like git, it's no practical problem as the gitignore file filters out the dependencies. If you tend to just zip your folders and copy and paste projects this'll will feel horrible. Best you manually copy the project contents and exclude 'node_modules' and 'bower_components' as you will use 'npm install' and 'bower install' respectively to install them elsewhere. Also have fun deleting those file paths that exceed window's limit to handle. You'll have to google 'mklink' to help you clear them out.

Praxia · August 25th, 2015, 04:38 PM

Quote:

Originally Posted by dougal83

You're right, it is normal. The node and bower modules recursively keep their own copies of their dependencies in a tree of folders. This behaviour seems to be a bone of contention within the community.

If you're using source control like git, it's no practical problem as the gitignore file filters out the dependencies. If you tend to just zip your folders and copy and paste projects this'll will feel horrible. Best you manually copy the project contents and exclude 'node_modules' and 'bower_components' as you will use 'npm install' and 'bower install' respectively to install them elsewhere. Also have fun deleting those file paths that exceed window's limit to handle. You'll have to google 'mklink' to help you clear them out.

Great advice, Dougal. Thanks!