json1 KB

Source map index map (sections with offsets)

An index map: instead of a top-level `mappings` string it carries a `sections` array of offset-and-map pairs, the form used when several independently built chunks are concatenated. For testing decoders that assume every map has mappings at the root.

Web assets Code parsing JSON parsing

Preview — first 49 linesjson

{
  "version": 3,
  "file": "app.bundle.js",
  "sections": [
    {
      "offset": {
        "line": 0,
        "column": 0
      },
      "map": {
        "version": 3,
        "file": "app.bundle.js",
        "sourceRoot": "",
        "sources": [
          "src/greet.js",
          "src/index.js"
        ],
        "sourcesContent": [
          "export function greet(name) {\n  return `Hello, ${name}!`;\n}\n",
          "import { greet } from \"./greet.js\";\nconsole.log(greet(\"world\"));\n"
        ],
        "names": [
          "greet",
          "name"
        ],
        "mappings": "MAAOA,WAAeC,GACpB,qBCAF,YAAYD"
      }
    },
    {
      "offset": {
        "line": 2,
        "column": 0
      },
      "map": {
        "version": 3,
        "file": "app.bundle.js",
        "sources": [
          "src/base.css"
        ],
        "sourcesContent": [
          ".card {\n  color: #059669;\n  border-radius: 12px;\n}\n"
        ],
        "names": [],
        "mappings": "AAAA,MACE,cACA"
      }
    }
  ]
}

Specifications

Seed: 70400
Site: example.com (fictional)
Version: 3
Kind: index map
Sections: 2
Offsets: line 0 and line 2
Nested Maps: 2

Testing contract

Expected to pass

Scenario: Decode a map that has `sections` and no top-level `mappings`.
Expected result: Both nested maps are read and their segments shifted by their section offset, so a position on generated line 2 resolves through the second section rather than the first.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Source map index map (sections with offsets)” is a deterministic Novus Examples fixture for Web assets, Code parsing, JSON parsing. Favicons, web app manifests, service workers, robots and sitemap files, Open Graph images, and .well-known resources — for testing web tooling, crawlers, PWA installers, and asset pipelines.

Documented properties for this file: seed 70400. 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.

Web-platform fixtures are standards-compliant samples against fictional example.com data. Test crawlers, PWA installers and manifest validators, favicon/icon pipelines, service-worker registration, or .well-known parsers against the documented structure.

Code examples

import json

with open("sourcemap-index-sections.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/web_p7.py. Free for any use, no attribution required — license.