We journey into the somewhat nascent realm of front-end architecture to get some traction on how it might play an important role in building and maintaining the often complex modern frontend.
Web Unleashed 2019 in Toronto is a conference focused towards front-end web development with many great sessions ranging from technical to inspirational.
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.
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.
Native observers empower your JavaScript to subscribe to events like the alteration of the DOM, an elements position in relation to the viewport and even the resizing of individual elements.
While it’s not possible to learn every trick out there, I’ve found that dedicating time to learning something new about DevTools has improved my workflow and helped me debug faster.
