Skip to main content
interlace
Plugin: operability

Changelog

Release history and version updates for eslint-plugin-operability

Generated from the release history

Built from this package's CHANGELOG.md at deploy time, so it matches the version these docs describe. The full cross-package history lives on the changelog.

4.1.0

  • Fixconsole['log'] reaches the same sink as console.log
  • Fixprocess['exit']() is the same call as process.exit()
  • Fixres['send'](err.stack) leaks the same stack as res.send
  • Fixremaining console gates resolve a subscripted method
  • Maintenancethe verbose-error check no longer casts an unnameable member
  • Dependenciesupdated workspace dependencies: @interlace/eslint-devkit@1.19.0

4.0.1

  • FixAdd an install-size badge to the README prelude, linking to each package's packagephobia page. npm renders the README from the last publish, so a badge only appears on npmjs.com after a release.
  • Dependenciesupdated workspace dependencies: @interlace/eslint-devkit@1.18.2

4.0.0

Breaking
  • Breaking💥 Breakingrequire-data-minimization no longer guesses what your PII is
  • Feature✨ Featurerequire-code-minification gains minificationKeys
  • Dependenciesupdated workspace dependencies: @interlace/eslint-devkit@1.18.0

3.1.1

  • Fixpoint meta.docs.url at documentation that exists #683
  • Dependenciesupdated workspace dependencies: @interlace/eslint-devkit@1.17.2

3.1.0

  • no-console-log and no-debug-code-in-production no longer report code that #607
  • DependenciesUpdated internal dependencies

3.0.16

  • Correct the declared ESLint floor: ^8.0.0^8.40.0. #407
  • Correct the ESLint peer range shown in the README Compatibility table. #423
  • DependenciesUpdated internal dependencies

3.0.15

  • Ship the JavaScript without tsc's layout. #411
  • DependenciesUpdated internal dependencies

3.0.14

  • Load rule modules on demand instead of at plugin load. #381
  • Declare what we support, load only what we use #381
  • Fix the ./oxlint subpath export, which pointed at src/oxlint.js — a file no build produces. require('<package>/oxlint') threw MODULE_NOT_FOUND on every published package, while every README documented that exact wiring for oxlint's jsPlugins. The export now points at the build output, dist/src/oxlint.js. #335
  • DependenciesUpdated internal dependencies

3.0.13

  • Add the ecosystem and oxlint marks to the README logo row. Each plugin now #364

3.0.12

  • Re-publish every package so npm carries the optimised artifact #338
  • DependenciesUpdated internal dependencies

3.0.11

  • Rewrite description and keywords on every published package for npm search discovery. npm ranks on name, description, and keywords, and the registry only picks up these fields at publish — so this is metadata-only and takes effect for each package on its next release. #294
  • DependenciesUpdated internal dependencies

3.0.10

  • Docsdocs: dual-logo README header (Interlace mark + ESLint mark side by side) and closing Interlace footer — refreshes the README rendered on npmjs.com. No runtime changes. #269
  • DependenciesUpdated internal dependencies

3.0.9

  • Fix Codecov badge showing "unknown" — switch from flag to component URL format #252

3.0.8

  • CI-only: pin all coverage thresholds at 100% (integration target, merges last). #225

3.0.7

  • Fixfix: republish recommended preset with the correct plugin namespace #200

3.0.6

  • Fixfix: republish recommended with correctly-namespaced, unscoped rule ids #197
  • align codecov component IDs with full package names
  • fix changelog header format across all packages
  • Ofri Peretz

3.0.4

  • align codecov component names and update docs components
  • Ofri Peretz

3.0.3

  • 📘 Launched new documentation site: eslint.interlace.tools
  • 📝 Achieved 100% documentation parity (both .md and .mdx files)

1.0.0

  • Initial stable release with 6 production-readiness rules
  • LLM-optimized error messages for AI-assisted development
  • 100% test coverage across all rules
  • ESLint 9 flat config support
  • TypeScript type definitions for all rule options
  • recommended - Balanced operability checks for production code
  • no-verbose-error-messages prevents information exposure (CWE-209)
  • require-data-minimization enforces data protection principles
  • Converted skeleton documentation to high-fidelity guides
  • Added comprehensive examples for all rules
  • Documented known limitations in docs/KNOWN-LIMITATIONS.md

4.1.1

  • FixThe README logo now links to the plugin's own documentation.

Building secure JavaScript with Interlace? Star the repo to get new rules and CWE coverage as we ship them — or follow the AI-code-security benchmarks behind them.