builds

This post details as to why I wanted to implement Semantic-UI-React into our Revision.net project. It was not however as simple as I would have liked as a result of our build process. Such that heavy Javascript (that is regularly utilised across the site) can be cached (and served

Today I decided that it was worth investing some time in revisiting the build tools that are used across the Double Negative web properties. We use gulp pretty much universally across our projects. In fact not only do most projects use gulp, but most projects use very similar build processes

My current build process for PubReviews.com utilizes Grunt. On occasion I have seen 'Esprima' outputted within my build logs. I have always been happy to allow the internals of the tools which I utilize for build and release cycles to keep their internals relatively hidden. That was until today.