Files
zeekayandHanzo Dev 7543364826 Let the test suite run, and point the sitemap at our own host
jest.config.js has named jest-environment-jsdom since the Jest 28 upgrade
split it out of core, but it was never added to devDependencies, so `jest`
refused to start and the two suites had not run in a long time. Installing it
at 29.7.0 alongside the jest already here exposed the next layer: jest.setup.js
imports @testing-library/jest-dom/extend-expect, an entry point v6 dropped in
favour of the package root.

The tests also read as untyped to tsc, which has no idea what describe or
expect are without @types/jest. Its matchers still came up short afterwards:
jest-dom registers toBeInTheDocument from jest.setup.js, a file outside the
program, so the reference now sits in additional-types.d.ts where tsc will see
it and the tests type-check against the matchers they run against.

siteUrl was still the starter template's, so robots.txt handed crawlers
tsnext-tw.thcl.dev as the canonical host and every URL in the sitemap pointed
somewhere we do not own. public/CNAME and the README both say the site is
foundation.zoo.ngo. The regenerated sitemap also drops /team/, a page removed
in 4a3543a that the committed copy still advertised.

The three .tsx.orig files were merge leftovers. Nothing imports them, and the
versions they held are in history.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-04 00:29:49 -07:00

4 lines
192 B
XML

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap><loc>https://foundation.zoo.ngo/sitemap-0.xml</loc></sitemap>
</sitemapindex>