Anatomy of a Collection
Between two application releases not all files are changed and not all files require optimization process to be run on every build, and specially vendor files which change maybe once between several releases.
The new build process can recognize parts in big production files which already have been optimized in a previous build.
Now because the explanation above reads like any other Gulp changed/incremental plugins description we’ll use speed measurements to show how these improvements are different from others you’ve probably seen.
This gets built/optimized/minified in 5.57 min, so that’s a normal build time.
Now I changed 10 CoffeeScript (which build slower) files and run build again, and now we have a build time of 20 s !
So in this case we have 94% faster build!
And if I were to change more files we could probably get slower then this.
This is one example, but depending on your application you will probably see improvement of around 85% and more in build speeds.
This also means that your CI builds can run much faster, deployment can be much faster, and many other possibilities can be open (like watch mode with production settings, or streaming updates to production).
We will call this feature “swaped-incremental builds“.
As with previous releases, there are no breaking changes. Just go ahead and run:
npm install laravel-basset@~1.5.0