Doesn't recognize next.config.mjs

[pratv1]

It works fine with the js extension:

Run actions/configure-pages@v3
  with:
    static_site_generator: next
Injecting property=basePath and value= in:
/** @type {import('next').NextConfig} */
const nextConfig = {
  output: "export",
};

...but when I have a next.config.mjs, it ignores it and makes up a new config file on its own:

Run actions/configure-pages@v3
  with:
    static_site_generator: next
Using default blank configuration
Injecting property=basePath and value= in:
// Default Pages configuration for Next
const nextConfig = {}
module.exports = nextConfig

[2chanhaeng]

I had a similar problem to yours for a similar reason.
Recently, when I create a project with create-next-app, it generates next.config.mjs instead of next.config.js.
So I think this issue could be going bigger and should be fixed sooner rather than later.
Additionally, I temporarily fixed the issue by deleting next.config.js just before the build like following:

      - name: Build with Next.js
        run: |
          rm -f next.config.js
          ${{ steps.detect-package-manager.outputs.runner }} next build

[OtmaniCodes]

is a solution found to this issue?

[pratv1]

@OtmaniCodes I ended up commenting out this line from the build step to make it work:

You can check my workflow file for reference.

[OtmaniCodes]

@OtmaniCodes I ended up commenting out this line from the build step to make it work:

You can check my workflow file for reference.

Thank you

[JamesMGreene]

The available workaround is to provide the path in your Actions workflow via the generator_config_file input parameter, e.g.:

- name: Setup Pages
  uses: actions/configure-pages@v4
  with:
    static_site_generator: next
    generator_config_file: ./next.config.mjs

For now, I'll leave this issue open to look at auto-detecting alternative file paths. It's not something we'd prioritize highly, but it isn't an unreasonable expectation given the behind-the-scenes magic this action is already attempting to take care of on users' behalf. 🤷

[JamesMGreene]

A fix for this is now included in actions/configure-pages@v5. 🚀

e.g.

- name: Setup Pages
  uses: actions/configure-pages@v5
  with:
    static_site_generator: next

[imbirdperson]

I'm still getting the error after tyring all the above solutions. I'm new to JavaScript world. Can some one help me identify the problem. Below is the github action error. But I'm able to build the page locally without any errors.

'''Run actions/configure-pages@v5
Injecting property=output and value=export in:
import { createRequire } from "module";
const require = createRequire(import.meta.url);
const withMDX = require('@next/mdx')({
extension: /.mdx?$/,
});

/** @type {import('next').NextConfig} */
const nextConfig = {
output:'export',
distDir:'dist',
images:{
unoptimized: true,
},

pageExtensions: ['js', 'jsx', 'mdx', 'ts', 'tsx'],

};

export default withMDX(nextConfig);

Error: TypeError: error must be an instance of Error'''

[richardtorres314]

A fix for this is now included in actions/configure-pages@v5. 🚀

e.g.

- name: Setup Pages
  uses: actions/configure-pages@v5
  with:
    static_site_generator: next

@JamesMGreene The fix works well when there's no import, but seems to break when importing a dependency (or at least the @next/bundle-analyzer as I've tried). For example, in a next.config.mjs file:

// @ts-check

import NextBundleAnalyzer from '@next/bundle-analyzer';

const withBundleAnalyzer = NextBundleAnalyzer({
  enabled: process.env.ANALYZE === "true",
});

/** @type {import('next').NextConfig} */
const nextConfig = {
 output: "export"
};

export default withBundleAnalyzer(nextConfig);

results in the configure-pages action erroring out with the message, "TypeError: error must be an instance of Error".

Commenting the static_site_generator: next line seems to resolve the type error.

A minor inconvenience, but a workaround suffices. Glad to see the project continued adoption!