feat: oxlint 1.0 release post

Author: camc314

.vitepress/config/en.ts

@@ -23,7 +23,7 @@ export const enConfig = defineLocaleConfig("root", {
       {
         text: "Resources",
         items: [
-          { text: "Blog", link: "/blog/2025-03-15-oxlint-beta" },
+          { text: "Blog", link: "/blog/2025-06-01-oxlint-stable" },
           { text: "Team", link: "/team" },
           { text: "Branding", link: "/branding" },
           { text: "Website GitHub", link: "https://github.com/oxc-project/oxc-project.github.io" },

.vitepress/sidebar.blog.json

@@ -1,4 +1,8 @@
 [
+  {
+    "text": "Oxlint Stable",
+    "link": "/blog/2025-06-01-oxlint-stable"
+  },
   {
     "text": "Oxlint Beta",
     "link": "/blog/2025-03-15-oxlint-beta"

.vitepress/theme/components/Banner.vue

@@ -16,7 +16,7 @@ const hide = () => {
   document.documentElement.classList.add("banner-dismissed");
 };
 
-const slug = "/blog/2025-03-15-oxlint-beta";
+const slug = "/blog/2025-06-01-oxlint-stable";
 
 const bannerDismissed = useLocalStorage<boolean>(`oxc-banner-dismissed-${slug}`, false);
 
@@ -45,7 +45,7 @@ const dismiss = () => {
 
 <template>
   <div ref="el" class="banner banner-dismissed">
-    <div class="text"><a :href="slug">Announcing Oxlint Beta</a> 🎉</div>
+    <div class="text"><a :href="slug">Announcing Oxlint</a> 🎉</div>
 
     <button type="button" @click="dismiss">
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor">

src/blog/2025-06-01-oxlint-stable.md

@@ -0,0 +1,150 @@
+---
+title: Oxlint 1.0
+outline: deep
+authors:
+  - camc314
+---
+
+<AppBlogPostHeader />
+
+After eighteen months of dedicated development and hundreds of contributions from our community, Oxlint 1.0 is here! This milestone represents our commitment to building a production-ready linter that developers can rely on.
+
+Oxlint is a Rust-powered linter for JavaScript and TypeScript that ships with 500+ built-in rules and is designed to be fast, extensible, and simple to adopt. Unlike many side projects that come and go, Oxlint has been our full-time focus—we've invested deeply in creating a tool that meets the demanding needs of modern JavaScript development.
+
+## Quick Start
+
+Getting started with Oxlint is straightforward. Run it in your codebase using your preferred package manager:
+
+::: code-group
+
+```sh [npm]
+$ npx oxlint@latest
+```
+
+```sh [pnpm]
+$ pnpm dlx oxlint@latest
+```
+
+```sh [yarn]
+$ yarn dlx oxlint@latest
+```
+
+```sh [bun]
+$ bunx oxlint@latest
+```
+
+```sh [deno]
+$ deno run npm:oxlint@latest
+```
+
+:::
+
+Oxlint is configurable via an .oxlintrc.json file. Each source file is linted with the nearest configuration, and you can use overrides to target specific glob patterns. You can also extend shared configs to keep teams consistent.
+
+For more detailed instructions on how to use Oxlint and integrate it with your project or editor, check out the [installation guide](/docs/guide/usage/linter).
+
+## Highlights
+
+**Comprehensive Rule Coverage**
+Oxlint includes over 500 carefully implemented rules from trusted sources:
+
+- Complete ESLint rule set, including TypeScript-specific rules from typescript-eslint
+- Popular plugin rules from `eslint-plugin-unicorn`, `eslint-plugin-jsdoc`, `eslint-plugin-react`, `eslint-plugin-react-hooks`, `eslint-plugin-jest`, and `eslint-plugin-import`
+- Unique Oxlint rules like [bad comparison sequence](../docs/guide/usage/linter/rules/oxc/bad-comparison-sequence), [const comparisons](../docs/guide/usage/linter/rules/oxc/const-comparisons), and [only used in recursion](../docs/guide/usage/linter/rules/oxc/only-used-in-recursion)
+
+**Flexible Configuration**
+Configure Oxlint through `.oxlintrc.json` files with support for:
+
+- Nested configurations that apply to specific directories
+- Override patterns for targeting specific file types or locations
+- Shared configuration extending for team consistency
+
+**Editor Integration**
+First-class editor support with extensions for:
+
+- [VS Code](https://marketplace.visualstudio.com/items?itemName=oxc.oxc-vscode)
+- [IntelliJ IDEA and WebStorm](https://plugins.jetbrains.com/plugin/27061-oxc)
+- [Zed Editor](https://zed.dev/extensions?query=oxc)
+- Language server protocol support for other editors
+
+![CLI Demo](./oxlint-cli-demo.gif)
+_Oxlint running in the terminal with detailed error reporting_
+
+![VS Code Integration](./oxlint-vscode.png)
+_Real-time linting feedback in VS Code_
+
+## Adoption
+
+**From ESLint**: Migrating from ESLint is seamless. Oxlint uses familiar configuration patterns and rule names, making the transition smooth for existing projects.
+
+**For New Projects**: Start fresh with modern defaults. Oxlint's built-in rule set covers common patterns and best practices out of the box.
+
+**In CI/CD**: Integrate Oxlint into your build pipeline for fast, reliable code quality checks that won't slow down your deployment process.
+
+**For Large Codebases**: Scale confidently with Oxlint's performance-first architecture that handles monorepos and large JavaScript applications efficiently.
+
+For detailed adoption guidance, see our [installation guide](/docs/guide/usage/linter).
+
+## Performance
+
+We benchmarked Oxlint vs ESLint on large, real-world codebases using the same rule configurations to measure performance under consistent conditions.
+
+### Repository Benchmark Summary
+
+| Repository         | File count | Lint time | Commit Hash                                  |
+| ------------------ | ---------- | --------- | -------------------------------------------- |
+| `microsoft/vscode` | 5,955      | 0.356s    | (`1a99a26db899152df71fcfd1914e63804d5d0d57`) |
+| `elastic/kibana`   | 71,160     | 1.948 s   | (`f635e2a3b06526195d393b67f0d4534ce792815e`) |
+
+### Linting Visual Studio Code
+
+For a more direct comparison, we ran Oxlint and ESLint on the Visual Studio Code codebase using exactly the same enabled rules and configurations.
+
+```sh
+hyperfine --warmup 3 'oxlint -c .oxlintrc.json' './node_modules/.bin/eslint -c eslint2.config.js' -i
+```
+
+Oxlint was compiled in release mode at commit e2f0f0a.
+
+| Tool   | Time     |
+| ------ | -------- |
+| oxlint | 603.1 ms |
+| eslint | 36.597   |
+
+Summary
+
+⚡ Oxlint ran ~60x faster than ESLint on the same codebase and configuration.
+
+This demonstrates Oxlint’s dramatic performance advantage when linting large codebases, making it a compelling drop-in replacement for ESLint in CI pipelines and local development.
+
+## Roadmap
+
+**Custom Rules** – JavaScript plugin support is coming soon, enabling teams to write custom rules that integrate seamlessly with Oxlint's architecture.
+
+**Performance Optimizations** – Continued improvements to parsing and analysis speed.
+
+## Acknowledgements
+
+Oxlint 1.0 represents the collective effort of over 200 contributors who have shaped this project. We're grateful for every bug report, feature request, and code contribution.
+
+Special recognition goes to:
+
+- [@branchseer](https://github.com/branchseer) for implementing the multi-file analysis runtime.
+- [@camc314](https://github.com/camc314), [@mysteryven](https://github.com/mysteryven), and [@shulaoda](https://github.com/shulaoda) for implementing many sophisticated lint rules, testing, and constantly improving everything.
+- [@camchenry](https://github.com/camchenry) for implementing nested configuration support.
+- [@DonIsaac](https://github.com/DonIsaac) for improving configuration, documentation and website, and for representing Oxc at [SquiggleConf 2024](https://2024.squiggleconf.com).
+- [@leaysgur](https://github.com/leaysgur) for the RegExp parser and JSDoc plugin.
+- [@Sysix](https://github.com/Sysix) for maintaining `eslint-plugin-oxlint` and significant contributions to the language server and VSCode extension.
+- [@u9g](https://github.com/u9g) and [@rzvxa](https://github.com/rzvxa) for implementing control flow graph analysis.
+
+We'd love to hear your feedback on Oxlint! Please reach out to us on [Discord](https://discord.gg/oxlint) or [GitHub Discussions](https://github.com/oxc-project/oxc/discussions) with any questions, suggestions, or issues you encounter. Your input is invaluable in helping us make Oxlint even better.
+
+## Join the Community
+
+We're excited to see how Oxlint helps improve your development workflow. Connect with us:
+
+- **Discord**: Join our [community server](https://discord.gg/9uXCAwqQZW) for real-time discussions
+- **GitHub**: Share feedback on [GitHub Discussions](https://github.com/oxc-project/oxc/discussions)
+- **Issues**: Report bugs or request features on our [issue tracker](https://github.com/oxc-project/oxc/issues)
+
+Your feedback drives Oxlint's evolution. Let's build better JavaScript tooling together.