chore: bump @nuxtjs/sitemap version

[preschian]

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.

👇 __ Let's make a quick check before the contribution.

PR Type

• Bugfix
• Feature
• Refactoring

Context

• Related Problems with Nitro x Cloudflare Pages #9107

Currently, this is the root cause of the renovate throw error. try to run this command on main branch:

npx nuxi upgrade -f && NITRO_PRESET=cloudflare_pages pnpm nuxi build

now, try to run that command again in this branch

Did your issue had any of the "$" label on it?

• My DOT address: Payout

[netlify]

✅ Deploy Preview for koda-canary ready!

Name	Link
🔨 Latest commit	a8077d6
🔍 Latest deploy log	https://app.netlify.com/sites/koda-canary/deploys/65b32eb56570070008e1e5f5
😎 Deploy Preview	https://deploy-preview-9140--koda-canary.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[reviewpad]

AI-Generated Summary: This pull request includes updates to both the package.json and nuxt.config.ts files. In the package.json file, changes involve swapping the "nuxt-simple-sitemap" package for the "@nuxtjs/sitemap" package indicating a shift in the method for the generation of sitemaps. In the nuxt.config.ts file, the previous 'nuxt-simple-sitemap' module was replaced with the '@nuxtjs/sitemap' module. This suggests that the sitemap has been migrated to a more advanced, possibly feature-rich version provided by the NuxtJS team. Additionally, the hooks for sitemap generation have been removed, which implies reliance on the capabilities of the newly integrated '@nuxtjs/sitemap' module, rather than managing it programmatically through the hook.

[reviewpad]

Reviewpad Report

⚠️ Warnings

• Please link an issue to the pull request

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@fortawesome/fontawesome-svg-core@6.5.1	None	+1	1.18 MB	robmadole
npm/@histoire/plugin-vue@0.17.9	Transitive: environment, eval, filesystem, network, shell, unsafe	+198	131 MB
npm/@nuxtjs/sitemap@5.0.5	Transitive: environment, eval, filesystem, network, shell, unsafe	+799	254 MB	harlan_zw
npm/@types/node@20.11.6	None	+1	4.06 MB	types
npm/@typescript-eslint/eslint-plugin@6.19.1	Transitive: environment, eval, filesystem, shell, unsafe	+118	83.2 MB	jameshenry
npm/@typescript-eslint/parser@6.19.1	Transitive: environment, eval, filesystem, shell, unsafe	+113	80.2 MB	jameshenry
npm/histoire@0.17.9	Transitive: environment, eval, filesystem, network, shell, unsafe	+175	50.1 MB
npm/wavesurfer.js@7.7.0	None	0	536 kB	katspaugh
npm/workbox-window@6.6.1	environment	+2	856 kB	tropicadri

🚮 Removed packages: npm/@fortawesome/fontawesome-svg-core@6.4.2, npm/@histoire/plugin-vue@0.17.8, npm/@types/node@20.11.5, npm/@typescript-eslint/eslint-plugin@6.19.0, npm/@typescript-eslint/parser@6.19.0, npm/histoire@0.17.8, npm/nuxt-simple-sitemap@3.4.1, npm/wavesurfer.js@7.6.5, npm/workbox-window@6.6.0

View full report↗︎

[codeclimate]

The PR diff size of 6505 lines exceeds the maximum allowed for the inline comments feature.

[codeclimate]

Code Climate has analyzed commit a8077d6 and detected 0 issues on this pull request.

View more on Code Climate.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Native code	npm/bufferutil@4.0.8	Location: Package overview	package.json pnpm-lock.yaml

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/bufferutil@4.0.8

[yangwao]

Thanks!
pay 30 usd

[yangwao]

😍 Perfect, I’ve sent the payout
💵 $30 @ 6.55 USD/DOT ~ 4.58 $DOT
🧗 1xjvRADwdJcnmUCLWerEHR4iGCT5EBTm4D4fzLLg4LcAC9p
🔗 0x0146f636c2de2f02ef9f5997674a1d8daf5006b1b36be1f186b46e81281e6885

🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues