Why separate builds into public and build in gulp(grunt)?

Question

JavaScript

The question was inspired by this post habrahabr.ru/post/208890

It's just that in fact it's the same thing, or maybe I don't understand something. I didn’t work with a grant myself, and even with a gallop, but yesterday I already passed a mini-course, I will implement it on Monday, so I’m trying to figure out what structure to build for the project.

Answer 1

There are different ideologies for building projects. Be it dev, dist, public, production or any other folders. But the main difference between these assemblies is the following: in the above example, presumably, public is the assembly of the project for debugging, and build is for production, where the source files are minified (for example, JavaScript), and at the same time, the debugging process becomes much more complicated when instead of the pointer you are used to a pointer is issued for an unknown minified code point.

Answer 2

In public, files from SASS/LESS/HAML/... will be compiled, but in a readable form, this is done to speed up the compilation and editing process itself.
In build, files are not only compiled, but also minified, images are compressed, SASS is passed through an autoprefixer, and so on.

Answer 3

Your temporary files get into public when developing a project. Here, in my jade template, the files are rendered in html to the .tmp folder, and when I do gulp build, this folder is in gitignore. Something like this.