Additional i18n Paths

[rayferric]

Google suggests to create one <url> section for every path including the localized versions. At this current moment, next-sitemap only generates <url> sections for the default locale paths and this increases the number of lines in the sitemap N times relative to non-localized sitemap, where N is the number of supported languages. On the other hand, Google's approach would cause the number of lines to be (N^2)-rupled.
next-sitemap does not create those duplicate entries, but that makes me worried about whether such approach will result in bad international SEO. Now the question is: "should I be concerned?"

How next-sitemap handles this situation (pseudocode):

url=en:
   hreflang=en ...
   hreflang=de ...

What Google expects me to do:

url=en:
   hreflang=en ...
   hreflang=de ...
url=de:
   hreflang=en ...
   hreflang=de ...

Here's the article on Google Developers' Portal:
https://developers.google.com/search/docs/advanced/crawling/localized-versions

Here's my next-sitemap config:

/** @type {import('next-sitemap').IConfig} */
const config = {
  siteUrl: process.env.NEXT_PUBLIC_ORIGIN,
  generateRobotsTxt: true,
  alternateRefs: [
    {
      href: process.env.NEXT_PUBLIC_ORIGIN,
      hreflang: 'en'
    },
    {
      href: process.env.NEXT_PUBLIC_ORIGIN + '/de',
      hreflang: 'de'
    }
  ]
};

module.exports = config;