mirror of
https://github.com/zoo-apps/foundation.git
synced 2026-10-30 14:57:26 +00:00
zeekayandHanzo Dev
7543364826
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]>
13 lines
344 B
JavaScript
13 lines
344 B
JavaScript
/**
|
|
* @type {import('next-sitemap').IConfig}
|
|
* @see https://github.com/iamvishnusankar/next-sitemap#readme
|
|
*/
|
|
module.exports = {
|
|
/** Without additional '/' on the end. Matches public/CNAME. */
|
|
siteUrl: 'https://foundation.zoo.ngo',
|
|
generateRobotsTxt: true,
|
|
robotsTxtOptions: {
|
|
policies: [{ userAgent: '*', allow: '/' }],
|
|
},
|
|
};
|