Sourcemap Explorer

Sourcemap Explorer is a learning tool for web developers and students. It does two things, both passively and locally.

1. Sourcemap inspector. When a site ships JavaScript sourcemaps to production, the extension detects them automatically. The toolbar icon turns green and clicking it shows a virtual tree preview of the original project — the same tree you get in the downloaded zip. One click saves a single .zip with every original source, deduplicated across bundles.

2. Tech-stack detector. A second tab in the popup lists the frameworks, libraries, CDNs, analytics, CMS, payment providers, build tools and programming languages running on the current site, with version numbers where available. Detection uses the same fingerprint database as Wappalyzer (vendored from the open-source enthec/webappanalyzer fork) plus extra signals extracted from sourcemaps — so we surface libraries the live page doesn't expose at runtime.

Highlights
- Passive detection. The icon stays gray by default and turns green the moment a sourcemap is spotted on the current site.
- Cumulative per-site cache. Scope is grouped by registrable domain (eTLD+1), so subdomains and CDNs roll up together.
- Clean virtual tree preview, deduplicated across bundles and with webpack synthetic modules filtered out. What you see is what ends up in the zip.
- One-click download of the reconstructed project as a single .zip file.
- Stack tab: frameworks, meta-frameworks, UI/CSS libraries, state libs, build tools, languages, WordPress plugins & themes (enumerated by slug), Next.js-ecosystem packages, hosting providers, analytics and more.
- Ad-hoc package detection. Any npm package present in a sourcemap but not covered by a built-in rule shows up under "JavaScript libraries" with its version, after a minimal existence check against the npm registry.
- Custom rules options page. Add, edit, export and import your own fingerprints as JSON.
- Third-party isolation. Analytics, ad and tracking, do not contribute their internal libraries to the current site's detected stack.

Use cases
- Study how a production app is structured — the tree in the zip is the original src/ folder.
- Read the original TypeScript or JSX behind a minified bundle.
- Answer "what framework/version is this site on?" without guessing.
- Audit which analytics/tracking/ad services a site loads.
- Learn production architecture by reading real code instead of tutorials.