Husky

First, install Prettier locally:

...It's part of the job....

An API explorer for RESTful Hypermedia APIs using HAL or HAL-FORMS - toedter/hal-explorer

No more unexpected type errors!

Defensive Commits are a strategy for pushing commit to upstream repos that runs part of the ci/cd pipeline locally using git hooks. It fails the hook fails. This allows you to catch integration errors and get feedback quickly. This strategy works best with trunk-based development and ci/cd teams, because it helps avoid breaking the build and reduces dumb mistakes from even being pushed up to main. At Coqui Health, we’ve implemented this strategy successfully and this is now the default way we work. We use a monorepo strategy coupled with ci/cd and trunk-based development, which means we work close to or in trunk and so having a robust ci/cd pipeline is paramount. Defensive commits allows us to catch bugs early and get feedback that our code will work or break things. It’s allowed us to move faster and not break things.

Complete your GitHub Action journey by building production artifacts, implementing semantic versioning, and creating automated release pipelines that verify your action works in real-world conditions before reaching users.

In this fun tutorial, let's see how Git hooks work by creating 5 different hooks with Husky, a popular JavaScript package.

This post shows you how to setup up accessibility linters in Vue 3.

This is not an article that Steve, the author, thinks should exist in a healthy industry, but the shape of our industry — especially right now — makes this sort of article very necessary and hopefully helpful to you in your job.

Here are some tools and libraries that are really useful for your frontend app. You should at least be aware of them so when you need them, you know what tool to look for.

echo $RANDOM. Exploring Software and writing about it.

Git hooks made easy 🐶 woof! Contribute to typicode/husky development by creating an account on GitHub.

First, install Prettier locally:

How to make your local git config stop you from pushing slightly broken code live by mistake.

An adventure in configuring automated tooling to catch spelling mistakes in my website

Complete your GitHub Action journey by building production artifacts, implementing semantic versioning, and creating automated release pipelines that verify your action works in real-world conditions before reaching users.

It may seem silly, but it's important to me that my Tailwind classes are orderedly consistently, and I don't want to have to manage that manually. Frustratingly, I've never found a solution that gives me exactly what I want—until now. Here's my must-have list: Works in CLI/Continuous Integration (Rustywind would work here, but not Headwind) Works in all IDEs (so Headwind doesn't cut it, and Rustywind would require work to adapt) Uses Tailwind's official ordering specifications (again, Headwind/Rustywind would require work to get here) Works on Laravel Blade files I've asked on Twitter multiple times, and the most recent time I asked, I got a response from my friend Jason Beggs suggesting I should look into prettier-plugin-blade. So I set out, with Jason's help, to get it working on a new Laravel app, later receiving some help from the tools' creator, John. What I found is that the ideal solution to my wish list above is using prettier-plugin-blade together with Tailwind's official Prettier plugin. It works on CI and the CLI, has IDE integrations, works in Blade files, and uses Tailwind's official class ordering. Let's dig in! The installation Install prettier, prettier-plugin-tailwindcss, and prettier-plugin-blade with npm install npm install --save-dev prettier-plugin-blade@^2 prettier prettier-plugin-tailwindcss Add a .prettierrc config file to your project root Here is the most basic file you'll start with, before you start actually configuring Prettier: { "plugins": ["prettier-plugin-blade", "prettier-plugin-tailwindcss"], "overrides": [ { "files": [ "*.blade.php" ], "options": { "parser": "blade" } } ] } On top of this, you can add your own lines to configure Prettier; here are those I've added, but you can find more here. { "printWidth": 120, "semi": true, "singleQuote": true, "tabWidth": 4, "trailingComma": "all", "plugins": ["prettier-plugin-blade", "prettier-plugin-tailwindcss"], "overrides": [ { "files": [ "*.blade.php" ], "options": { "parser": "blade" }

I'm a webdeveloper and I have found that I use a lot of different technologies. To put it into perspective, I thought I would make a list of all the technologies, tools, frameworks, libraries, languages, stacks, services, etc., that I've personally used at some point in my career. 🔣 Languages & Protocols

Walking through the process of getting my personal blog off the ground.

I’ve spent more time over the last 20 years working on front-end asset pipelines than I’d care to admit. One thing that kept coming up when inheriting older ...

I was looking into setting up Husky + lint-staged for a new Deno library that I recently open-sourced, when I came across a project called Lefthook. Unlike the duo, this is a single Go binary which can manage git hooks and run commands against staged files. Also unlike the duo, this is agnostic of the project language and doesn’t require having a package.json file. This intrigued me—two birds with one stone and all that.

Exactly ten years ago, I gave a talk at the SF JavaScript meetup titled 5 Kung Fu Moves for Front-End Heroes. A full decade later, I found myself wondering: are these techniques still the secret sauce for modern front-end engineering, or have they been rendered obsolete by time?

A technical write-up on my journey migrating from ESLint + Prettier to Biome