PACKAGE · LINTING & FORMATTING

@rslint/core

rslint core library

WEEKLY DOWNLOADS 26.1K
STARS 431
FORKS 25
OPEN ISSUES 66
GZIP SIZE 88.5 kB
UNPACKED SIZE 2.3 MB
DEPENDENCIES 3
LAST UPDATED 27d ago
DOWNLOAD TRENDS

@rslint/core downloads — last 12 months

Download trends for @rslint/core1 download series from Aug 2025 to Jul 2026. Use left and right arrow keys to inspect monthly values.026.6K53.3K79.9K106.6KAug 2025NovFebMayJul 2026
@rslint/core
ABOUT @RSLINT/CORE

RSLint is a new, fast, and robust JavaScript and TypeScript linter designed to be a modern alternative to existing tools. It addresses the common pain points of slow linting performance and complex configuration that plague many development workflows. By offering a high-performance engine written in Rust, RSLint aims to provide near-instantaneous feedback during development, allowing developers to catch errors and style issues as they type rather than during lengthy build processes.

The core philosophy behind RSLint prioritizes speed, correctness, and a more intuitive developer experience. It targets modern JavaScript and TypeScript projects, including those utilizing newer language features and frameworks. The project is built on the idea that linting should be a seamless part of the development process, not a bottleneck. This makes it particularly appealing to developers who value rapid feedback loops and efficient tooling.

RSLint's architecture leverages a pluggable rule system and a sophisticated AST (Abstract Syntax Tree) traversal mechanism. While specific APIs are not detailed in the provided metadata, its design implies a clear separation between parsing, analysis, and reporting. Developers can expect to interact with configuration files to enable or disable specific rules and customize linting behavior, similar to other established linters, but with an emphasis on performance derived from its Rust core.

Integration points for RSLint typically involve build systems, code editors, and CI/CD pipelines. It is designed to work within common JavaScript and TypeScript development ecosystems. Its categories include "Linting & Formatting" and topics such as "javascript-linter," "linter," and "typescript-linting," indicating compatibility with standard linting workflows and potentially integrating with tools that expect specific output formats.

With a weekly download count of 23.1K and 429 GitHub stars, RSLint shows growing adoption and community interest. Its unpacked size is 2.3 MB, with a gzipped bundle size of 88.5 kB, indicating a relatively moderate footprint for its capabilities. As of its last update in 2026-07-29, the project has 54 open issues, suggesting active development and areas for community contribution or potential stabilization.

Developers should be aware that RSLint, while rapidly developing, may still be maturing compared to more established linting solutions. The presence of 54 open issues indicates ongoing development and potential for undiscovered bugs or missing features. While its core functionality is robust, some niche configurations or less common JavaScript/TypeScript patterns might not yet be fully supported or might require specific rule configurations.

WHEN TO USE
  • When needing highly performant linting feedback integrated directly into code editors, reducing feedback loops.
  • When working with modern JavaScript and TypeScript projects that benefit from fast static analysis.
  • When seeking a linter with explicit "Linting & Formatting" categories and topics that align with standard code quality tooling.
  • When the size of the linting tool is a consideration, with a gzipped bundle size of 88.5 kB.
  • When migrating from or exploring alternatives to established linters that may present performance challenges.
  • When contributing to or utilizing a project with active development, indicated by 54 open issues and 23.1K weekly downloads.
WHEN NOT TO USE
  • If only a single, minimal code style check is required, simpler, more focused tools might suffice.
  • If extensive, highly customized linting rules for very old JavaScript environments are a primary need, as newer tools may prioritize modern features.
  • If absolute stability and a vast ecosystem of pre-made plugins for obscure scenarios are paramount, consider more mature linters.
  • If integration with custom build tools that strictly expect legacy linter output formats proves difficult without significant adapter work.
  • If the project's dependencies are extremely sensitive to package size and even an 88.5 kB gzipped bundle is prohibitive.

CORRECTIONS

Spot wrong data here?

A short note helps us fix it.

Anonymous · No account · No email back

COMPARISONS 6
@rslint/core vs prettier ★ 52.2K · 106.5M/wk @rslint/core vs dprint-node ★ 491 · 1.3M/wk @rslint/core vs @biomejs/biome ★ 25.5K · 10.1M/wk @rslint/core vs ultracite ★ 3.1K · 631.4K/wk @rslint/core vs oxlint ★ 22.2K · 12.0M/wk @rslint/core vs eslint ★ 27.4K · 129.2M/wk