Source map v3 for a stylesheet
The v3 map for the minified stylesheet: one source with its text inlined, an empty names array, and three segments covering the selector and both declarations. For testing that a decoder handles maps with no names at all.
{
"version": 3,
"file": "styles.min.css",
"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
- Sources
- 1
- Names
- 0
- Sources Content
- true
- Mapping Segments
- 3
Testing contract
Expected to pass- Scenario
- Decode a map whose `names` array is empty.
- Expected result
- All three segments decode as four-field segments, no name lookup is attempted, and column 6 of the generated line resolves to src/base.css line 2 column 3.
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 v3 for a stylesheet” 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-css-v3.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonapple-app-site-associationAn Apple app-site-association file declaring Universal Links, web credentials, and app clips — normally served without an extension at /.well-known/, for testing AASA parsers (shown here as .json).
- jsonassetlinks.json (Android)An Android Digital Asset Links file granting app-link handling to a package via a certificate fingerprint (sample) — for testing assetlinks.json parsers and App Links verification.
- jsonFeed twin - JSON Feed 1.1The third twin: the same four articles as JSON Feed 1.1, using the 1.1 `authors` array rather than the 1.0 singular form, with ids, URLs, summaries, HTML bodies and timestamps identical to the RSS and Atom files. The reference output for an XML-to-JSON feed converter.
- jsonhost-meta.json (JRD, JSON form)The JSON Resource Descriptor twin of the XRD host-meta: identical subject, alias, expiry, property and three links, expressed with lower-case JSON member names. For testing XRD-to-JRD conversion against a known answer.
- jsonJSON-LD — Breadcrumb SAMPLEschema.org JSON-LD SAMPLE (breadcrumb) for SEO/structured-data validators.
- jsonJSON-LD — Faq Page SAMPLEschema.org JSON-LD SAMPLE (faq-page) for SEO/structured-data validators.
Generated by generation/web_p7.py. Free for any use, no attribution required — license.