Site profile
react-tokyo.vercel.app
Built with mealz-components 3.2.8, gtag, @marimo-team/frontend 0.25.0, mirador 4.2.4, @zappway/embeds 2.0.28. 5 pages and 15 stored files, last crawled 2026-10-03.
5 libraries 1 identifier 32 third-party hosts 1 crawl open the site
Technologies and libraries
Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.
| Library | Version | Seen |
|---|---|---|
| mealz-components | 3.2.8 | 2026-10-03 |
| gtag | 2026-10-03 | |
| @marimo-team/frontend | 0.25.0 | 2026-10-03 |
| mirador | 4.2.4 | 2026-10-03 |
| @zappway/embeds | 2.0.28 | 2026-10-03 |
Tracking, tag and verification IDs
Public identifiers read out of the source. Each links to every other site in the index that carries the same one.
| What | Value | Found in |
|---|---|---|
| Google Analytics 4 measurement id (Google) | G-VQNGS1YC35 | view source |
Third-party hosts
Hosts outside react-tokyo.vercel.app that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.
Stored pages and scripts
The newest stored version of each file, newest first@if (p.FilesTruncated) {
Timeline
One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.
-
first crawl
5 pages, 15 files, 779.9 KB; 5 libraries, 1 identifier, 32 third-party hosts
5 libraries added
- gtag
- mirador 4.2.4
- @marimo-team/frontend 0.25.0
- @zappway/embeds 2.0.28
- mealz-components 3.2.8
1 identifier added
- G-VQNGS1YC35 Google Analytics 4 measurement id
32 third-party hosts added
15 files added
- https://react-tokyo.vercel.app/ html
- https://react-tokyo.vercel.app/blogs html
- https://react-tokyo.vercel.app/about html
- https://react-tokyo.vercel.app/fes2026 html
- https://react-tokyo.vercel.app/members html
- https://react-tokyo.vercel.app/assets/(basic)-DD_-JZEY.js js
- https://react-tokyo.vercel.app/assets/index-f5GByVoz.js js
- https://react-tokyo.vercel.app/assets/compiler-runtime-DkfZN4Fj.js js
- https://react-tokyo.vercel.app/assets/utils-VY7sMv4X.js js
- https://react-tokyo.vercel.app/assets/client-Md3ycoHO.js js
- https://react-tokyo.vercel.app/assets/_layout-C4TeZ2mG.js js
- https://react-tokyo.vercel.app/assets/main-DtqMt9ot.js js
- and 3 more
Questions about react-tokyo.vercel.app
- How does PageSourceSearch know what react-tokyo.vercel.app is built with?
- From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
- How far back does the history of react-tokyo.vercel.app go?
- To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
- Can I see an older version of a script from react-tokyo.vercel.app?
- Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
- Which other websites use the same tracking IDs as react-tokyo.vercel.app?
- Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.
Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.