A pre-commit is a type of Git Hook that runs before each commit. It can help with verifying code standards (linting, formatting, testing etc.).
A tool written in Python, though can be used with projects in any language. Can be configured to run many hooks including pre-commit/pre-commit-hooks and Gitleaks. I have used this tool and like it for Python and other projects, though for Node.js projects, I prefer the options below.
A pre-commit hooks tool written in JavaScript. I prefer this tool for Node.js projects since it can be easily integrated in package.json scripts.
Another tool that’s written in JavaScript, to help run checks against staged files (see Guide below). Lint-staged does not configure git pre-commit hooks on its own, but can be combined with Husky.
Another git hooks manager written in JavaScript. Use to be more lightweight than Husky, but newer versions of Husky closed the gap.
Configure oxlint and oxfmt based on my Oxc Workflow.
Install devDependencies:
npm install --save-dev husky lint-stagedhusky:# Installed
./node_modules/.bin/husky --init# Not installed
npx run husky --initlint-staged to run Oxc and tsc checks:[/**
* @filename: lint-staged.config.js
* @type {import('lint-staged').Configuration}
*/
export default {
'**/*.[jt]s?(x)': [
'oxfmt',
'oxlint --type-aware --type-check --fix',
],
'**/*.ts?(x)': () => 'tsc -p tsconfig.json --noEmit',
}Can be further configured, but this is a good start for a project using TypeScript and Oxc.
husky to run lint-staged as a pre-commit hook:npm exec -- lint-staged --config lint-staged.config.jspreparescript in package.json : "scripts": {
"prepare": "husky"
},husky --init.
I wrote about Oxc (The JavaScript Oxidation Compiler) in Next Generation Tooling for Developers. When I first wrote this article, Oxc already included a linter (oxlint, which can replace ESLint), but the formatter was not available yet. Since then, VoidZero has continued the development of Oxc, not only launching Vite+ but also launching a formatter (oxfmt, which can replace Prettier). With the combination of oxlint and oxfmt, I now have a modern-alternative to ESLint + Prettier. Note that this might not work as a replacement in all existing projects that rely on specific configurations of ESLint and/or Prettier. However, for new Node.js projects, I will strive to go with the Oxc stack.
The two main reasons I prefer Oxc is speed and ease of configuration; as I have explained in Next Generation Tooling for Developers, the Rust-based tools are noticeably faster. In addition, they have a more modern design with more intutive configuration. In particular, ESLint has become a nightmare to configure after the breaking changes in ESLint v9.
These tools can be run in a project without being installed or added to package.json using npx commands:
npx oxlint@latestnpx oxfmt@latestFor consistent usage in an npm project, Oxc packages can be added as devDependencies.
npm install --save-dev oxlint@latest oxlint-tsgolint@latest oxfmt@latestConfiguration files for Oxlint are written in JSON, with support for comments (JSONC). Oxlint will automatically search for files named .oxlintrc.json and automatically use those. But you can name the file anything when you are using the --config CLI option.
Use the --init option to initialize a .oxlintrc.json file:
## If installed
./node_modules/.bin/oxlint --init## If not installed
npx oxlint@latest --initBy default, oxfmt automatically tries to find the nearest .oxfmtrc.json or .oxfmtrc.jsonc file from current working directory. If not found, default configuration is used.
Also you can specify your config file by -c yourconfig.jsonc flag.
Almost all format options are compatible with Prettier’s options. So you may finish your setup by just renaming .prettierrc.json to .oxfmtrc.jsonc.
Use the --init option to initialize a .oxfmtrc.json file:
## If installed
./node_modules/.bin/oxfmt --init## If not installed
npx oxfmt@latest --init--init option).
The prettier-init tool can be used to help bootstrap configuration:
npx prettier-init@latest
mv ".prettierrc.json" ".oxfmtrc.json"scripts block in package.json
For easy and consistent usage across the project, add to the scripts block in package.json:
"scripts": {
"lint": "oxlint --type-aware --type-check .",
"lint:fix": "oxlint --type-aware --type-check . --fix",
"lint:fix-all": "oxlint --type-aware --type-check . --fix --fix-suggestions --fix-dangerously",
"format": "oxfmt .",
"format:check": "oxfmt . --check"
},Commit and push all relevant files that were changed or added:
git add ".oxfmtrc.json" ".oxlintrc.json" "package.json" "package-lock.json"
git commit -s
git pushFeatured image by Gabriel Heinzer on Unsplash.
]]>I am not focusing on AI tools in this article. I have other articles on this subject (such as Agentic CLI Tools Comparison).
The projects below have a few things in common. The projects are led by companies which have similar missions to develop modern tooling for developers. All of the tools below are open-source under the MIT License.
Most of the tools are written in modern compiled languages such as Rust or Go. Many of the tools boast significant performance improvements compared to previous tools, as well as a more modern design with better Developer Experience (DX or DevEx).
As a result, these tools tend to feel both faster and easier to use than the tools that they aim to replace.
Astral’s Mission
We build high-performance developer tools for the Python ecosystem.
Our mission is to make the Python ecosystem more productive.
By building tools that enable developers to ship great software, faster.
Tools that change how we work.
Rye is another tool that was maintained by Astral, however it is no longer developed and uv is considered “the successor project from the same maintainers”.
The Mission
We are building a unified high-performance toolchain for JavaScript: including parser, transformer, resolver, linter, formatter, minifier, bundler, test runner, and meta framework support. Our mission is to make the next generation of JavaScript developers more productive than ever before.
Web Infra
We are from ByteDance, our goal is to build an open technical ecosystem to promote the development of frontend technology.
All of the tools mentioned above are primarily developed and maintained by companies. This raises the question, if the tools are FOSS (Free and Open Source), what are their business models?
ByteDance of course owns TikTok. They make enough money already and can afford contributing to open-source if they so chose. My theory is that ByteDance likely wants to continue contributing to open-source to put them in the same positive light as Western tech companies (for example Meta, who developed many open-source projects including React, Docusaurus and Llama).
On the other hand, Astral and VoidZero are both venture-backed. While they can afford to lose money for a period while gaining users, eventually they will want to find a way to extract value. In the past, when the founders of the companies were asked about this, they gave somewhat vague statements.
However, more recently, Astral introduced pyx (a Python-native package registry):
Beyond the product itself, pyx is also an instantiation of our strategy: our tools (uv, Ruff, ty, etc.) remain free, open source, and permissively licensed — forever. Nothing changes there. Instead, we’ll offer paid, hosted services like pyx that represent the “natural next thing you need” when you’re already using our tools: the Astral platform.
It is likely that VoidZero will go for a similar strategy in the future, by introducing paid services that go alongside the free tools.
The tools themselves are still FOSS, and all are licensed under the permissive MIT License. These companies know that if they ever attempt to change the license or terms for these tools, the community will immediately fork the projects (as has happened many times in the past with other open-source projects).
UPDATE: VoidZero has launched Vite+.
I have listed a lot of tools from these companies, of course I have not tried all of the tools mentioned above.
I have been using Astral’s projects, uv and Ruff, and had good experience with both, and I want to try ty as well. As I’m getting more into TypeScript development with React, Docusaurus and Cloud Development Kit (CDK), I have been trying out some of the TypeScript tools as well.
In the case of Docusaurus, I tried Docusaurus Faster which uses Rspack (by Web Infra), as well as SWC and Lightning CSS. This makes it almost as fast as Rspress (another project by Web Infra). The difference in build times is immediately noticeable compared to building Docusaurus with Webpack.
The speed difference is also felt in uv; compared to pip, uv downloads the same packages noticeably faster. I have further explained my love for uv in uv is incredible.
Ruff works well as both a Linter and Formatter. Ty does the same for type checking in Python.
Besides the speed, I have also noticed these tools tend to be easier to use than the older, less modern tools that the aim to replace. The focus on Developer Experience (DX or DevEx) is apparent.
Recently, I have been trying out TypeScript Linters and Formatters and wrote about the Rust Alternatives. Oxc looks promising, it currently has a Linter, while the Prettier-compatible Formatter is still under development. Once the Formatter is ready, I will try using Oxc (instead of ESLint + Prettier), at least for projects that don’t require specific ESLint plugins that aren’t yet supported by Oxc.
Out of all the projects I listed here, Vite is probably the most widely used. It’s popular enough to have gotten its own documentary: Vite: The Documentary - YouTube
I have been using Vite for React apps, notably CALMe. Ever since create-react-app has been deprecated, I have been consistently seeing Vite as one of the top recommendations, including in the React Documentation: Creating a React App and Build a React app from Scratch.
Vite is being integrated with Rolldown: Rolldown Integration | Vite
Featured image by Anton Savinov on Unsplash.
]]>