Does not work with Next 13

[qaribhaider]

Describe the bug
Added and configured the package on a NextJS 13 project with Prismic CMS, it logs in the console Generating Sitemap message, but does not create any file

To Reproduce
Steps to reproduce the behavior:

1. Create a new Prismic project based on Next 13
2. Add and configure the library on it
3. Build or run the project as dev
4. Check the public folder for the generated sitemap, where no sitemap file is found

Expected behavior
Public folder has the sitemap.xml file

Desktop (please complete the following information):

• OS: MacOS

[ReeceM]

Hi @qaribhaider just checking is it the latest version that you are using?

[qaribhaider]

Hey @ReeceM, yes I used the latest version

[ReeceM]

So I just did a test on a project I'm running the package on with Next 13.1.6 and it is generating the sitemap.

Is it possible that you have provided a different public path for it to write too?

Or maybe is it possible to share the next.conf.js file?

[qaribhaider]

I tried manually specifying the public path, but it didn't help

Below is my next.config.js

const nextConfig = {
  reactStrictMode: false,
  images: {
    domains: ['api.lorem.space', 'images.prismic.io'],
  },
  poweredByHeader: false,
};

// The Prismic API endpoint
const API_ENDPOINT = `https://${process.env.REPOSITORY_NAME}.cdn.prismic.io/api/v2`;

// The hostname of the website, for example it would be https://example.com
const SITE_URL = process.env.VERCEL_ENV;

// this is the link resolver for the documents that are fetched
const linkResolver = (doc) => {
  switch (doc.type) {
    case 'homepage':
      return '/';
    case 'page':
      return `/${doc.uid}`;
    case 'topic':
      return doc.data.page
        ? `/topic/${doc.uid}/${doc.data.page}`
        : `/topic/${doc.uid}`;
    default:
      return null;
  }
};

const withPrismicSitemap = require('@reecem/prismic-sitemap')({
  linkResolver: linkResolver,
  apiEndpoint: API_ENDPOINT,
  hostname: SITE_URL,
  optionsMapPerDocumentType: {
    page: { changefreq: 'monthly', priority: 1 },
    topic: { changefreq: 'monthly', priority: 1 },
  },
  documentTypes: ['homepage', 'page', 'topic'],
});

module.exports = withPrismicSitemap({
  ...nextConfig,
});

[ReeceM]

Thanks for sharing I will give it a spin in my site to see as well 👍

[ReeceM]

Do you want to try version 0.5.3, possibly there might have been an issue where there wasn't a type and it was getting stuck in a loop trying to resolve empty promises.

[qaribhaider]

Thank you, updating to 0.5.3 seems to have fixed the issue, and it is generating the sitemap now. You can mark this as solved.

However, I do have a question, if you can let me know why is this run as a dev dependency?
For me, I have a site that gets regenerated every time I publish something on Prismic CMS, wouldn't that make the sitemap outdated?

[ReeceM]

Glad it is working.

Regarding the question. When your site is regenerated from publishing is it the whole site or incremental building? If your Nextjs site rebuilds like normal on a prismic publish event then the sitemap is rebuilt as the build step from Vercel/Netlify runs with the dev dependency and it updates the sitemap. Is it not doing that at the moment?

The one reason is that it isn't meant to be directly bundled with final code as I haven't tested it that way.

[qaribhaider]

It's combined for me, some pages are static while some are incremental.

The sitemap generator seems to run fine locally, publishes and even updates the sitemap with the build command, but on Vercel it's not updating or publishing the sitemap (however its printing in the logs about sitemap generation)