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

First Look: Bazel build system

Google has an interesting build system for their internal applications and projects called Blaze. Bazel is the open-source version of that project. According to its documentation, Bazel offers the following advantages: High-level build language. Bazel uses an abstract, human-readable language to describe the build properties of your project. Unlike other tools, Bazel operates on the concepts of libraries, binaries, scripts, and data sets, shielding you from the complexity of writing individual calls to tools such as compilers and linkers Bazel is fast and reliable. Bazel caches all previously done work and tracks changes to both file content and build commands.

Playwright, a better Puppeteer?

I love Puppeteer, it’s almost the perfect tool to test sites and do screenshots of the projects we’re working on. It was originally a Chrome only tool, meaning it would only work with headless Chromium; it then graduated to working with headless Firefox as well… but Safari/WebKit is missing. This is the most basic example of using Puppeteer. It will navigate to a site and create a screenshot of the above-the-fold content. We can use Puppeteer to navigate the pages and simulate interactions const puppeteer = require(‘puppeteer’) const screenshot = ‘github-chromium.png’; (async () => { const browser = await puppeteer.launch({