Minified JS bundle with an inline base64 source map
The same bundle with its v3 map embedded as a base64 data: URI in the sourceMappingURL comment - the single-file form dev builds emit. For testing that a tool decodes an inline map instead of trying to fetch it as a relative path.
(()=>{function e(n){return`Hello, ${n}!`}console.log(e("world"))})();
//# sourceMappingURL=data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiYnVuZGxlLmlubGluZS1tYXAubWluLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsic3JjL2dyZWV0LmpzIiwic3JjL2luZGV4LmpzIl0sInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCBmdW5jdGlvbiBncmVldChuYW1lKSB7XG4gIHJldHVybiBgSGVsbG8sICR7bmFtZX0hYDtcbn1cbiIsImltcG9ydCB7IGdyZWV0IH0gZnJvbSBcIi4vZ3JlZXQuanNcIjtcbmNvbnNvbGUubG9nKGdyZWV0KFwid29ybGRcIikpO1xuIl0sIm5hbWVzIjpbImdyZWV0IiwibmFtZSJdLCJtYXBwaW5ncyI6Ik1BQU9BLFdBQWVDLEdBQ3BCLHFCQ0FGLFlBQVlEIn0=
Specifications
- Seed
- 70400
- Site
- example.com (fictional)
- Source Mapping URL
- data: URI
- Encoding
- base64
- Map Bytes
- 444
- Original Sources
- 2
Testing contract
Expected to pass- Scenario
- Open a bundle whose sourceMappingURL is a data: URI.
- Expected result
- The base64 payload decodes to the same v3 map as the external fixture, no HTTP request is made, and positions resolve identically.
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
“Minified JS bundle with an inline base64 source map” is a deterministic Novus Examples fixture for Web assets, Code parsing, Syntax highlighting. 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 · base64. 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
node bundle.inline-map.min.jsRelated files
- jsService Worker (sw.js)A sample cache-first service worker handling install, activate, and fetch events with an offline fallback — for testing service-worker registration, JS parsers, and PWA tooling.

- cC — Hello WorldThe classic hello-world in C — an include, main, and printf — for testing highlighters, C compilers, and parsers against the canonical first program.

- cC — Linked list (structs, malloc, pointers)A realistic C program: a singly linked list with a typedef struct, malloc/free memory management, pointer walking, and error handling — for testing highlighters, compilers, and static analysers.

- cC StructC struct SAMPLE for clangd / highlighter fixtures.

- csC# FibonacciA small C# iterator Fibonacci utility — realistic snippet for language tooling.

- csC# HelloIdiomatic C# hello-world for syntax highlighters and Roslyn-style parsers.

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