CDS 2020: New CSS properties for performance

There are two new CSS properties that may help with the layout shift core vitals issue. The content-visibility property allows us to tell the browser when to render an element. The “magic” value here is auto, which tells the browser not to render an element until it’s visible in the viewport. This makes page loads significantly faster, the browser doesn’t need to render above-the-fold content initially. The content-visibility property works hand in hand with the contain-intrinsic-size property to prevent potential issues with Cumulative Layout Shift. Because the browser isn’t rendering the element fully on load, there may be some shift

Bazel Build System: Overall Notes and Observations

Bazel is hard to get to work but it’s really interesting to work with once you get started. Like Ant and other build systems I’ve worked with before they use their own terminology and their own tooling to make things work better for their intended audiences. These are some notes that I’ve collected along the way… they’ve informed my own research and are good things to keep in mind as you work with the tool and its ecosystem. Why Use Bazel In my opinion, Bazel works best in a monorepo with multiple languages attached, whether the monorepo builds a single

Bazel Build System: Backend code, even more choices

Just like with the frontend, the backend gives you multiple choices of languages and feature sets for working with Bazel. C/C++, Go and Rust are the three languages that I tested generating WASM code with so it may be interesting to see how well they work with Bazel and how they abstract WASM generation. We can keep all the code for our project in a single monorepo and let Bazel sort out what tools to use to compile which part. I use C and C++ as the baseline for testing Bazel with backend languages. It also works slightly differently from

Bazel build system: Frontend Styling

Bazel presents multiple choices for building your site or app’s styles. I’ve taken three of these choices for a deeper look. The first one, working with Less and Stylus, shows how to work with NPM packages. We could use the same techniques to work with other packages outside the Bazel toolchains, we’ll have to test to see if they work. The other two, PostCSS and SASS show how to work within the Bazel structure using Bazel toolchains and methodology. I haven’t decided which one to use for my projects; been thinking about moving away from SASS for a while but

Bazel build system: Typescript and Node.js

In the last post we looked at Bazel, what it is, installation on macOS using homebrew, and a Bazel-based project’s basic configuration. This post will look at using Bazel to run Typescript and Node.js builds using Bazel. Future posts will look at styling and backend toolchains Javascript, Typescript and Node.js To work directly with Javascript we’ll leverage two items Every Javascript file is also a legal Typescript file We’re already looking at implementing a Node.js based build system that will use Javascript/Typescript Before Bazel will work we need to install the following Node packages. npm i -D @bazel/protractor \ @bazel/rollup