Sitemap not replacing the url

Start by inspecting the mentioned sitemap.xml.tsx and faust.config.js files, then compare the Yoast-generated sitemap URLs with the Faust frontend URLs using the listed package versions. Reproduce the blank-list behavior when replacing the WordPress URL. Done means the sitemap remains populated and its links use the intended frontend URLs.

Description

I'm trying to update the url on the sitemap links, but with no luck, neither from the WP or the FE.

On the WP, I'm using the Yoast SEO plugin to generate the sitemap, and without any changes, the plugin provides with the normal WP url.

But, then, when I try to replace on the WP the link, the page returns a blank list, so I removed the replace function.

Although this is related to the Yoast plugin, on the FE, the Faust plugin is not replacing the BE link with the FE link, so this should also be validated from this plugin.

Versions:

"@apollo/client": "^3.10.4",
"@faustwp/blocks": "^4.1.0",
"@faustwp/cli": "^3.1.0",
"@faustwp/core": "^3.1.0",
"@wordpress/base-styles": "^4.49.0",
"@wordpress/block-library": "^8.35.0",
"@wordpress/style-engine": "^1.41.0",
"graphql": "^16.6.0",
"next": "^14.2.3",
"react": "^18.3.1",

For the faust.config.js :

import { setConfig } from "@faustwp/core";

import templates from "@/wp-templates";
import possibleTypes from "@/possibleTypes.json";

import { I18nPlugin, RelayPagination } from "@/plugins";

/**
 * @type {import('@faustwp/core').FaustConfig}
 **/

export default setConfig({
	templates,
	plugins: [new I18nPlugin(), new RelayPagination()],
	experimentalToolbar: true,
	possibleTypes,
	usePersistedQueries: true,
});

the sitemap.xml.tsx

I don't know if there is any other option I can try or if I have to change anything to make it work

Steps to reproduce

NA

Additional context

No response

@faustwp/core Version

^3.1.0

@faustwp/cli Version

^3.1.0

FaustWP Plugin Version

1.4.1

WordPress Version

6.6.2

Additional environment details

No response

Please confirm that you have searched existing issues in the repo.

• Yes