eslint-config

Clear and concise description of the problem As a developer using this project, I want to be compatible with Rslint so that I can leverage Rslint's Rust-powered high-performance linting runtime while retaining the convenience and rule conventions of this config preset. Rslint is an ESLint-compatible linter that follows the ESLint Flat Config specification and supports running most community ESLint plugins. However, it does not implement a subset of ESLint runtime APIs — including custom parsers, config processors, type-aware parser services, and code path analysis hooks — that relies on for full functionality. Currently, using the full preset directly with Rslint will fail or silently skip large numbers of rules due to these unsupported APIs. I am willing to help contribute implementation or testing for this feature if the maintainers are open to this compatibility support. Suggested solution We could add an optional Rslint-compatible mode / preset within the config package: 1. Add runtime detection for the Rslint environment, and automatically disable features that depend on unsupported ESLint APIs when running under Rslint, including: Type-aware TypeScript rules that rely on Custom parsers configured via (e.g. , custom parsers for markdown/JSON/YAML) Config-level options used for Vue SFC and multi-block file linting Rules that depend on code path analysis APIs 2. Export a dedicated preset entry that only includes rules and integrations verified to work with Rslint's supported API surface, so users can import it directly for out-of-the-box compatibility. 3. Ensure core static analysis and stylistic rules (built-in ESLint rules, , , import-related rules etc.) remain fully functional, as they are compatible with Rslint's supported API set. Alternative Alternative solutions considered: 1. Instead of built-in runtime detection, provide a standalone documentation page with a step-by-step guide for manually adapting to work with Rslint, including a clear list of compatible rules/integrations and the exact config overrides needed to disable incompatible features. 2. Publish a separate companion package (e.g. ) that ships a preconfigured, Rslint-optimized rule set, keeping the main package unchanged. Additional context Official Rslint ESLint plugin compatibility documentation: https://rslint.rs/guide/eslint-plugins Rslint fully supports the ESLint Flat Config format (the same format used by for ESLint v9+). Standard rule APIs including , , token/comment/scope analysis, autofix (), and editor quick fixes all work normally in Rslint. The unsupported ESLint APIs in Rslint are: , custom , config , and code path analysis hooks ( / etc.). Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Clear and concise description of the problem I'd like to add security canaries to this repo for monitoring and detecting supply chain attacks, and protecting the wider community. A great example of the benefits of canaries in protecting the community is seen in this Grafana post, and research Detecting the Modern Supply Chain Attack: High-Fidelity Canaries for CI/CD. I'm happy to raise the PR and implement it myself (see below). Suggested solution There's a free Tracebit Community Edition GitHub integration you can install here that sets this up in under 5 minutes - once you do, it injects canary tokens (decoy credentials that look real but nothing legitimate ever uses) into every running build. If anyone tries to use one, you get an alert straight away. Since no real process ever touches them, a trigger means there's likely an issue. Alternative _No response_ Additional context I'm also more than happy to raise a PR and implement it myself. No stress if it doesn't fit - thought it would be useful to share with the wider community. Full disclosure: I work for Tracebit and built this myself. Our Community Edition is fully designed with community in mind and will remain free forever. Thanks, Gemma Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

https://github.com/antfu/eslint-config/blob/20dd434ad89d6994fcd114b362bf0b8b16de68df/src/configs/react.ts#L106 Issue is that NextJS isn't detected when using a monorepo. I think local-pkg doesn't recognize that I have "next" in my ./apps/web/package.json so eslint is throwing errors for