electrovir

The tools we use as developers make us more effective (or at least hopefully faster) developers.

A simple script: grep -rl '<search-string>' <search/dir> | xargs code -r Between two different directories: cd <first-path> && grep -rl '<search-string>' <search/dir> | (cd <second-path>; xargs code -r)

ffmpeg -i video.mp4 -c:v libvpx -crf 30 -b:v 0 -c:a libvorbis video.webm

c8 is my preferred package for calculating code coverage in Node.js testing and it is also apparently used by web-test-runner.

Here's an example of an existing production application's database testing setup in a TypeScript, Node.js backend.

If you look at the import.meta docs on MDN you'll notice that it says: The spec doesn't specify any properties to be defined on it, but hosts usually implement the following properties: [url, resolve] So what is actually in there?

Node.js now has a built-in test runner, which I've now tried, and it's fantastic!

ESM does not populate the __filename and __dirname variables frequently used in CommonJS.

element-vir is a package for defining and rendering custom HTML web components.

Web Components are reusable, native chunks of shared HTML, CSS, and JavaScript.

PickDeep is a utility type that expands TypeScript's built-in Pick utility type to pick keys in nested objects.

There are tons of options for test packages and frameworks within the JavaScript ecosystem, both on the backend and frontend.

A collection of commands for use in PostgreSQL.

Here's a super simple, low cost pattern for keeping track of multiple solo projects: just add a todo.md file at the root of each repo.

This is intended to be a very basic high level overview of GraphQL, explained to a developer that already understands the basics of REST API design.

If you're using TypeScript and ESLint in VS Code, wip files or legacy files can quickly explode into a sea of red squiggles, making it hard to know where to start or track what's going on.

This blog is built using Docusaurus in blog-only mode.

Day 1 of using Docusaurus and I'm already pretty disappointed in it.

Use {@link VarName} in JSDoc comments when referencing variables or types to get: "Rename Symbol" support in VS Code "Go to Definition" support in VS Code "Find All References" support in VS Code generated doc links to the original reference (in packages…