James Garbutt

With the rise of AI, life in tech is vastly different than it was just a few years ago.

Over the last couple of years, we’ve seen significant growth of the e18e community and a rise in performance focused contributions because of it.

This is just some of what I’ve been pondering recently - particularly in terms of how we ended up with such overly-granular dependency trees.

I haven’t written on this blog in some time, and most of my posts here are very technical (more like tutorials).

Recently I have been working on improving a whole bunch of web components in one of our code bases.

stylelint + lit-element = good times As some of you know, lately I’ve been very much involved in a few linting projects as well as spending plenty of time contributing to the linters themselves.

For some time, the common solution to linting a TypeScript project has been to use TSLint and the standard for linting JavaScript has quickly become ESLint.

Lately, I’ve been spending a bit of time moving a few different projects to use strict: true in the TypeScript compiler, as well as enabling a large amount of lint rules.

Deno?

This is going to be a brief one, just to keep a note somewhere of how to do these things and what they mean.