Postbuild opening config file instead of running next-sitemap

Hi!

I’ve installed next-sitemap (1.2.26) as a dev dependency, and added it to package.json: "postbuild": "next-sitemap".= However, when I build, the postbuild just opens the config file (next-sitemap.js) instead of executing next-sitemap.

Any ideas how to solve this?

Regards, TJ

[tomasg88]

Hello, Win 10 user over here. I was having the same issue where command postbuild: next-sitemap wouldn’t work.

Solution for me was renaming next-sitemap file and adding config flag, like this: postbuild: next-sitemap --config next-sitemap.config.js

Didn’t need to install cross-env

[MoltenCoffee]

The immediate cause seems to be the configuration file next-sitemap.js having the same name as the package itself. (With Node ignoring the .js part of course, in contrast with regular Windows behaviour). Node on windows seems to prioritize local files above known values in PATH.

This can be demonstrated by creating a next.js file inside the project directory, and then running the build script (npm run build, next build). It will act the same, trying to open this file instead of running the Next scripts.

Testing a workaround: When I edit next-sitemap/src/path/index.ts to include:

export const KNOWN_PATHS = {
  CONFIG_FILE: getPath('next-sitemap.config.js'),
}

instead of next-sitemap.js, and change the name of the config file accordingly, everything works as intended.

A solution? Of course this package could change its config file, to something like next-sitemap.config.js (which seems to a common format, as it is what Babel, PostCSS, Styleguidist, Next and many others offer (among other options)) but will present a breaking change. Adding it as a secondary config filepath for Windows-users could be an option as well.

I do find it peculiar I don’t seem to be able to find more examples like this online, although I get that developing on Windows might not be the greatest option out there.