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.
The way we often use Gulp can make our projects brittle and add friction that complicates contribution and on-boarding. Thankfully, this is an avoidable problem with a rock-solid solution that requires minimal effort.
The front-end domain has arguably reached a tipping point in its evolution that beckons its patrons to reconsider whether teams are structured optimally.
Serving dynamic content, while maintaining the cacheability of a Drupal 8 site, used to be a tedious task. Drupal 8 did introduce a Lazy Builder way back when, but using it requires a fair amount of coding. Instead, we’ll take advantage of the BigPipe module which was included as a stable module since Drupal 8.3.
JSConf is less than a week away and a solid contingent of Chromaticians will be headed to sunny California to soak up some of the exciting ways JavaScript is taking shape in the browser and beyond.
Internet Explorer still covers a statistically significant percentage of the current market share (as of the publication of this post) and front-end engineers would do well to recognize its caveats in order to solve problems quickly and deliver a great product to stakeholders.
We didn’t leave the retreat with a ten-step action plan, but together we came home with renewed energy and excitement about what’s next and how to keep our team growing in the ways that are important to us.
