IssueRaiser

JSON Schema validation in Node.js core

### What is the problem this feature will solve? Hi all, I wanted to open a discussion about whether JSON Schema validation could be a useful addition to Node.js core. ## Current state - Node.js currently has no built-in JSON Schema validation - `node.config.json` (experimental) uses hand-written type checking against a JSON Schema 2020-12 definition generated from C++ option metadata - `package.json` parsing uses simdjson but has no schema validation, fields are extracted structurally - The only schema validation in the Node.js tree lives inside `deps/npm` (Ajv) ## Potential use cases - Validate `node.config.json` against its own schema properly - Future validation for `package.json` fields (opt-in, non-breaking) - Expose as a built-in module (`node:jsonschema`) so userland doesn't need to pull in external validators ## Context I've been working on a project in this area, [ata-validator](https://github.com/ata-core/ata-validator), a JSON Schema validator built on simdjson and RE2. It currently passes 96.9% of the official JSON Schema Test Suite (Draft 2020-12) and falls back to a pure JS engine when native bindings aren't available. I'm not proposing to land it as-is, I'd love to hear from the group first: 1. Is there interest in having JSON Schema validation available in core? 2. What would be the most useful entry point? (config validation, public API, both?) 3. Any concerns about the dependency story? (RE2/abseil weight, simdjson already in core) Happy to share

Posted by mertcanaltin on Apr 5, 2026, 10:53 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Software)

JSON Schema validation in Node.js core

mertcanaltinApr 5, 2026, 10:53 AM

### What is the problem this feature will solve? Hi all, I wanted to open a discussion about whether JSON Schema validation could be a useful addition to Node.js core. ## Current state - Node.js currently has no built-in JSON Schema validation - `node.config.json` (experimental) uses hand-written type checking against a JSON Schema 2020-12 definition generated from C++ option metadata - `package.json` parsing uses simdjson but has no schema validation, fields are extracted structurally - The only schema validation in the Node.js tree lives inside `deps/npm` (Ajv) ## Potential use cases - Validate `node.config.json` against its own schema properly - Future validation for `package.json` fields (opt-in, non-breaking) - Expose as a built-in module (`node:jsonschema`) so userland doesn't need to pull in external validators ## Context I've been working on a project in this area, [ata-validator](https://github.com/ata-core/ata-validator), a JSON Schema validator built on simdjson and RE2. It currently passes 96.9% of the official JSON Schema Test Suite (Draft 2020-12) and falls back to a pure JS engine when native bindings aren't available. I'm not proposing to land it as-is, I'd love to hear from the group first: 1. Is there interest in having JSON Schema validation available in core? 2. What would be the most useful entry point? (config validation, public API, both?) 3. Any concerns about the dependency story? (RE2/abseil weight, simdjson already in core) Happy to share

Comments (0)

No comments yet. Start the discussion.

Comment on this issue