js64 B

JavaScript — Intentionally Invalid Syntax

Intentionally corrupt JavaScript object literal — labelled invalid for error handling. Labelled intentionally invalid in title and description.

Error handling Code parsing Editor testing

Preview, first 4 linesjs

const x = {
  a: 1,
  b: 2  // missing closing brace on purpose

Specifications

Language: javascript
Role: intentionally invalid
Valid: false

Testing contract

Expected to fail

Scenario: Run a JavaScript syntax check (node --check, or any ES parser) over the file.
Expected result: Parsing fails with SyntaxError: Unexpected end of input because the object literal opened on line 1 is never closed; the parser must report end-of-input rather than accepting a two-property object.

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

“JavaScript — Intentionally Invalid Syntax” is a deterministic Novus Examples fixture for Error handling, Code parsing, Editor testing. Deliberately corrupt and invalid files, clearly labelled, for testing how your tool fails.

Documented properties for this file: intentionally invalid · javascript · intentionally invalid. 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.