One of our core values at Chromatic is to “delight our clients”. There are numerous ways that we try to bring delight, but as developers and designers one of our most frequent deliverables is code; our particular development and quality assurance (QA) workflow helps us deliver high-quality code to our clients’ production environments more frequently, in smaller change-sets. This results in our clients seeing their requested changes more quickly, and when a bug does slip through (nobody’s perfect), we are able to identify it and squash it in record time. We attempt to automate as much of this process as possible saving more time for the pieces that require human touch.
At the time of Yarn’s debut, it brought big advancements to npm’s performance and workflow along with the introduction of lock files. A lot of time has passed since then and with the arrival of a native npm lock file, I was under the impression that more recent npm development had rendered the benefits of Yarn obsolete.
Chromatic has used Travis CI for nearly five years for our continuous integration needs; building every pull request, checking our changes against code standards, running automated tests, etc. On March 12, 2019, we canceled our Travis subscription and began running our builds elsewhere. Why make a change now? It’s simple, really.
Poor website architecture and performance planning has struck again, this time leaving 24,000 families in the state of Illinois disappointed and burdened by the crash of the Empower Illinois scholarship tax credit site.
dnscontrol is an open-source tool written in Go by the fine folks at Stack Exchange that allows us to configure our DNS records in a JS file that can be committed to version control and published on demand. With this configuration in git, we can now easily review changes through our normal pull request workflow, as well as getting a full log of any changes made over time.