next-sitemap: [next-sitemap] Unable to find export-maker
Describe the bug A clear and concise description of what the bug is.
I am receiving an error with next-sitemap. See attached images.
My project is being built directly from github to vercel.
It used to work but no longer does. I have no idea what went wrong though.
My next-sitemap.config.js config is as follows:
// https://www.npmjs.com/package/next-sitemap
/** @type {import('next-sitemap').IConfig} */
module.exports = {
siteUrl: 'https://myRealURLisHere/',
generateRobotsTxt: true, // (optional)
// ...other options
};
To Reproduce Steps to reproduce the behavior:
- Unknown
Screenshots If applicable, add screenshots to help explain your problem.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 20 (2 by maintainers)
@iamvishnusankar What is the solution for this? having same issue, how it is completed?
I removed
node_modules
andpackage-lock.json
, did a complete reinstall (npm i
), and … I’m still getting the error, on two different computers.Really frustrating bug.
P.S. I also added
swcMinify: true
; didn’t help.Thanks @7hakurg, at least now I got it to build successfully. Still can’t figure out why everything worked in the morning and the suddenly it wasn’t able to find the
export-maker
🤔There is a work around, in next-config, I updated swcMinify as True and this solved the issue for me for now.
This is one of those issues that I am facing for too long but haven’t been able to fix this. In my situation I am using Next 13.1.6 and Node 18*
I am using edge function on Vercel. If I remove the patch for edge function from the function that is export const config = { runtime: “edge”, };
My application builds in vercel but other wise it is not.
Be sure you run same versions locally and in Vercel, my issue was fixed upgrading node version from Vercel settings to 16
I isolated the problem to node 14, it works after updating to node 16. May be a combination of node 14 and next 13 for all I know 🤔