js94 B

Code Config — Eslint Flat Snippet

Tiny SAMPLE tooling config snippet (eslint-flat-snippet) for editor/linter harnesses.

Config parsing Editor testing Code parsing

Preview, first 4 linesjs

export default [
  { rules: { 'no-unused-vars': 'error', eqeqeq: 'error' } }, // SAMPLE
];

Specifications

Role: tooling-config
Wave: I

Testing contract

Expected to pass

Scenario: Import the file as an ESLint flat config and inspect the exported value.
Expected result: The default export is an array with one config object carrying exactly two rules, `no-unused-vars` and `eqeqeq`, both set to `error`. It is an ES module with no `require`, so loading it from a CommonJS context needs a dynamic import - flat config is ESM-first.

What is a .js file?

JavaScript (.js) is a plain-text source file for the JavaScript language: the scripting language of the web, also used server-side via Node.js. It is dynamically typed and event-driven, with first-class functions, prototypes, and (in modern syntax) modules, classes, and async/await.

How to use this file

Use an example .js file to test syntax highlighters, linters (ESLint), formatters (Prettier), bundlers, and JavaScript parsers, or as editor and diff-viewer fixtures.

How to use this file for testing

“Code Config — Eslint Flat Snippet” is a deterministic Novus Examples fixture for Config parsing, Editor testing, Code parsing. TOML and INI configuration files with nested sections and typed values, for testing config parsers and loaders.

Documented properties for this file: tooling-config. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

This is a short, known-correct source file. Run it through your syntax highlighter, linter, formatter, tree-sitter grammar, or parser, and open it in the in-browser editor to tweak and re-download. Each snippet exercises comments, string escapes, literals, and language keywords.

Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.