Compressed and non-compressed versions of js,css webpack?

When working on a simple website in a gulp, and generates compressed and non-compressed versions of files for later developers. In webpack , the task was more difficult. Is it possible to solve this problem and how? And if not how would be better to leave the source code of the project. The option of setting up git repo on the server will not work.
March 19th 20 at 08:31
1 answer
March 19th 20 at 08:33
I hope you realize that the generated files and "source" are two different things. And "subsequent developers" should convey exactly the source, and not something that you have nagraviroval.

The option of setting up git repo on the server will not work.

Is it really so hard to implement five commands and to provide the source code in a repository with all the explanations on the installation and the Assembly on one of the most popular sites like bitbucket, github?
At least give the source code archive.
Yes, I understand. It was about a simple website. I mean that there may be admitted anyone as a very green coder, so the backend decides that he can fix the button styles. Somnivayus that they will be for a couple of lines of css to dig into the sass files and then compress it. Such projects therefore I leave one css compressed and the other uncompressed but compiled with all the comments. )

Git repo is not suitable for the reasons described above it is already clear. - amani.Berge83 commented on March 19th 20 at 08:36

Find more questions by tags Webpack