Doesn't recognize next.config.mjs about configure-pages HOT 6 CLOSED

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

from configure-pages.

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

You can check my workflow file for reference.

from configure-pages.

@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

from configure-pages.

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. 🤷

from configure-pages.

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

from configure-pages.

is a solution found to this issue?

from configure-pages.