js118 B

Minified JS bundle referencing an external source map

A one-line minified bundle built from two ES modules, ending in the `//# sourceMappingURL=` comment that points at the v3 map shipped beside it. For testing that a debugger, error reporter or bundler analyser follows the annotation and resolves the map relative to the bundle.

Web assets Code parsing Syntax highlighting

Preview — first 3 linesjs

(()=>{function e(n){return`Hello, ${n}!`}console.log(e("world"))})();
//# sourceMappingURL=sourcemap-external-v3.json

Specifications

Seed: 70400
Site: example.com (fictional)
Generated Lines: 1
Source Mapping URL: sourcemap-external-v3.json
Original Sources: 2
Line Endings: LF

Testing contract

Expected to pass

Scenario: Load the bundle in a tool that resolves sourceMappingURL comments.
Expected result: The external map is fetched from the same directory and column 6 of the single generated line resolves to src/greet.js line 1, column 8.

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 referencing an external 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 · LF. 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.