Local guide to Gitignore, SemVer, source maps and WASM imports

Check Gitignore decisions against the intended root

Paste one root .gitignore and case-sensitive relative paths. Mark directories with a trailing slash. The report gives the final matching rule line and an excluded parent when that parent blocks a later negation. For *.log followed by !keep.log, a.log is ignored and keep.log is explicitly included.

A build/ rule followed only by !build/keep.txt still excludes build/keep.txt: the parent directory remains excluded. Supply a rule that also permits traversal when that is the intended policy. This check does not know tracked files, nested .gitignore files, global excludes or whether supplied paths actually exist. Combined rules and paths are limited to 1 MiB, 5,000 rules and 10,000 paths.

Use the same SemVer range and prerelease policy

Supply complete strict versions such as 1.2.0+build.2 and an npm range such as ^1.2.0. Blank range means *. The report preserves original strings and source lines, sorts by precedence and shows a null maximum when nothing matches. A list and range have a combined 1 MiB budget and at most 10,000 version lines.

Build metadata does not change precedence. Equal versions retain input order, so 1.2.0+build.2 and 1.2.0+build.1 remain tied; the first matching input wins maximum selection. The default npm policy excludes many prereleases unless the range admits their tuple. Turn on the visible prerelease option only when that wider policy is intended. Registry dist-tags and actual package availability are outside this supplied-list check.

Make generated files and column numbering explicit

Supply an ordinary v3 source map plus the generated filename and a stack or coordinate list. Stack columns are often displayed from one, while source-map original columns are zero-based. Choose the input column basis explicitly and keep it beside the mapped text. Wrong filenames, unmapped positions and unparsed lines remain visible in the complete report.

The combined map and frame budget is 5 MiB with at most 10,000 frames. Indexed section maps and malformed mappings are rejected. The mapper resolves recorded source paths and optional names locally, but does not fetch source URLs. Mapping a location is different from recovering a source file: absent sourcesContent cannot be reconstructed from coordinates.

Inspect WASM host names without running the module

Select a core .wasm binary up to 1 MiB. The current browser validates and compiles a Module, then lists import module names, import/export names and descriptor kinds. It never creates an Instance or calls an import, start function or exported function. The sample module provides a small repeatable import/export example.

A descriptor kind does not reveal a full function signature or prove that a host implementation is compatible. Empty names, Unicode names and zero-length descriptor lists are valid cases. Compilation rejection can mean damaged bytes or a feature unsupported by the current engine; use a compatible inspection environment before concluding that the binary is universally invalid.

Retain the complete output and recover deliberately

The visible tables preview at most 200 records. Download complete JSON or CSV for larger sets; source-map mapping also provides copyable mapped text. CSV spreadsheet protection may prefix dangerous cell values, while JSON retains original strings.

On an error, correct the reported path, version, mapping or binary rather than treating a partial table as a successful result. Keep the original file and input settings; a different root, range, filename or column basis can produce a different valid answer.

Before handing over the report

• Retain original inputs and the explicit settings.
• Check unmatched, unmapped and unavailable records.
• Download complete records when the table is truncated.
• Verify the receiving workflow uses the same root, range, coordinates or host contract.

Tools used in this article