Collect the project in development or in production?

A

Andrey Mensky2015-10-10 15:11:09

css

Andrey Mensky, 2015-10-10 15:11:09

Good afternoon everyone, please clarify for me a couple of questions regarding this...
I noticed that all sorts of gulp with grunt write devDependencies, therefore these modules are not available in production. It follows from this that the project should be collected in development and already sent a commit to production?
A question about assembling images, there are more than 150 images 512x by 512x, there are many pages on the site where more than 50 - 80 images are constantly loaded, how can you beat such download requests?

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

M

Mokhirjon Naimov, 2015-10-10
@zvermafia

If you go the pro way (and convenient), then I think you need to do this:
IMHO!!!

K

Konstantin Kitmanov, 2015-10-10
@k12th

Why are they not available in production? Are you doing npm install on prod? But how then do modules from just dependencies get to the production? OO
In general, it is possible this way, and that way. But so that the git does not swear at conflicts in the collected files, it is easier to put the build artifacts in .gitignore and build on the production.