The "next export" command has been removed in favor of "output: export" in next.config.js #58790

LuciferDIot · 2023-11-22T19:46:21Z

LuciferDIot
Nov 22, 2023

Summary

I was deploying in GitHub pages my Next.js application, which used threejs. I was getting this error again and again. So, I want to know what is the reason for this error and can someone guide me?

Additional information

My repository link: https://github.com/LuciferDIot/3D-Portfolio.git

Example

No response

Answered by jigneshloh

Feb 16, 2024

I was facing the same issue. commented cmd "static_site_generator: next" in deployment file nextjs.yml
Solved my issues.

View full answer

RenatMardanov · 2023-11-23T21:35:26Z

RenatMardanov
Nov 23, 2023

You can delete these 2 lines in nextjs.yml

name: Static HTML export with Next.js
run: ${{ steps.detect-package-manager.outputs.runner }} next export

and then update next.config.js as in the documentation at the link

9 replies

voidmain443 Jan 30, 2024

i had a same problam with the building workflow

i changed next.config.mjs file

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

julianesp Jan 31, 2024

Gracias. Se solucionó el error 👍

jigneshloh Feb 16, 2024

your answer helped me.

awaisYusuf Mar 5, 2024

unable to find nextjs.yml file. where that file is in next js project?

eliasgb2409 Mar 10, 2024

The nextjs.yml file is available in the .github directory that is created automatically when using GitHub Actions for hosting your Next.js project with Github Pages.

MShoaibCodes · 2023-12-05T07:14:49Z

MShoaibCodes
Dec 5, 2023

Where can I find nextjs.yml?

8 replies

LuciferDIot Dec 5, 2023
Author

Below is the code

`# Sample workflow for building and deploying a Next.js site to GitHub Pages

To get started with Next.js see: https://nextjs.org/docs/getting-started

name: Deploy Next.js site to Pages

on:

Runs on pushes targeting the default branch

push:
branches: ["main"]

Allows you to run this workflow manually from the Actions tab

workflow_dispatch:

Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages

permissions:
contents: read
pages: write
id-token: write

Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.

However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.

concurrency:
group: "pages"
cancel-in-progress: false

jobs:

Build job

build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Detect package manager
id: detect-package-manager
run: |
if [ -f "${{ github.workspace }}/yarn.lock" ]; then
echo "manager=yarn" >> $GITHUB_OUTPUT
echo "command=install" >> $GITHUB_OUTPUT
echo "runner=yarn" >> $GITHUB_OUTPUT
exit 0
elif [ -f "${{ github.workspace }}/package.json" ]; then
echo "manager=npm" >> $GITHUB_OUTPUT
echo "command=ci" >> $GITHUB_OUTPUT
echo "runner=npx --no-install" >> $GITHUB_OUTPUT
exit 0
else
echo "Unable to determine package manager"
exit 1
fi
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: "20"
cache: ${{ steps.detect-package-manager.outputs.manager }}
- name: Setup Pages
uses: actions/configure-pages@v4
with:
# Automatically inject basePath in your Next.js configuration file and disable
# server side image optimization (https://nextjs.org/docs/api-reference/next/image#unoptimized).
#
# You may remove this line if you want to manage the configuration yourself.
static_site_generator: next
- name: Restore cache
uses: actions/cache@v3
with:
path: |
.next/cache
# Generate a new cache whenever packages or source files change.
key: ${{ runner.os }}-nextjs-${{ hashFiles('/package-lock.json', '/yarn.lock') }}-${{ hashFiles('.[jt]s', '.[jt]sx') }}
# If source files changed but packages didn't, rebuild from a prior cache.
restore-keys: |
${{ runner.os }}-nextjs-${{ hashFiles('/package-lock.json', '/yarn.lock') }}-
- name: Install dependencies
run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
- name: Build with Next.js
run: ${{ steps.detect-package-manager.outputs.runner }} next build
- name: Upload artifact
uses: actions/upload-pages-artifact@v2
with:
path: ./out

Deployment job

deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v3`

JosemyDuarte Dec 10, 2023

Could it be that you are using a distDir different from out? Looks like the upload artifact is failing to find out. Maybe you are using dist. If that's the case you need to update the out to dist here:

uses: actions/upload-pages-artifact@v2
with:
path: ./out

josealvis Feb 2, 2024

If you are still having the problem be sure you do not have this line:
static_site_generator: next
This line overwrites your next.config file.

jigneshloh Feb 16, 2024

I was facing the same issue. commented cmd "static_site_generator: next" in deployment file nextjs.yml
Solved my issues.

Answer selected by LuciferDIot

md-fahad-ali Mar 25, 2024

still not work after commenting this one

davidde Feb 2, 2025

You also have to comment out the with: header of static_site_generator: next, because an empty field for with is invalid.

5267lq · 2023-12-09T16:50:34Z

5267lq
Dec 9, 2023

Maybe we deploy it on window platform but it's for ubuntu system. I meat the same problem.

5 replies

MShoaibCodes Dec 11, 2023

I tried deploying in an ubuntu server. Still the same issue occurred

Anth0nyQ Dec 12, 2023

@MShoaibCodes Please post your workflow file. I found that if your project is structured in a certain way you should put full paths and it works out.

MShoaibCodes Dec 12, 2023

on:
push:
branches:
- main

name: 🚀 Deploy website on push
jobs:
web-deploy:
runs-on: ubuntu-latest
name: 🎉 Deploy
steps:
- name: 🚚 Get latest code
uses: actions/checkout@v3

  - name: Use Node.js 18
    uses: actions/setup-node@v2
    with:
      node-version: "18"
      
  - name: 🔨 Build Project
    run: |
      npm install
      npm run export
      ls
      
  - name: 📂 Sync files
    uses: samKirkland/[email protected]
    with:
      server: ${{ secrets.HOST }}
      username: ${{ secrets.FTP_USERNAME }}
      password: ${{ secrets.FTP_PASSWORD }}
      port: ${{ secrets.PORT }}

MitoruDev Feb 9, 2024

I have the same error

`# Sample workflow for building and deploying a Next.js site to GitHub Pages

To get started with Next.js see: https://nextjs.org/docs/getting-started

name: Deploy Next.js site to Pages

on:

Runs on pushes targeting the default branch

push:
branches: ["main"]

Allows you to run this workflow manually from the Actions tab

workflow_dispatch:

Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages

permissions:
contents: read
pages: write
id-token: write

Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.

However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.

concurrency:
group: "pages"
cancel-in-progress: false

jobs:

Build job

build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Detect package manager
id: detect-package-manager
run: |
if [ -f "${{ github.workspace }}/yarn.lock" ]; then
echo "manager=yarn" >> $GITHUB_OUTPUT
echo "command=install" >> $GITHUB_OUTPUT
echo "runner=yarn" >> $GITHUB_OUTPUT
exit 0
elif [ -f "${{ github.workspace }}/package.json" ]; then
echo "manager=npm" >> $GITHUB_OUTPUT
echo "command=ci" >> $GITHUB_OUTPUT
echo "runner=npx --no-install" >> $GITHUB_OUTPUT
exit 0
else
echo "Unable to determine package manager"
exit 1
fi
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: "20"
cache: ${{ steps.detect-package-manager.outputs.manager }}
- name: Setup Pages
uses: actions/configure-pages@v4
with:
# Automatically inject basePath in your Next.js configuration file and disable
# server side image optimization (https://nextjs.org/docs/api-reference/next/image#unoptimized).
static_site_generator: next
- name: Restore cache
uses: actions/cache@v4
with:
path: |
.next/cache
# Generate a new cache whenever packages or source files change.
key: ${{ runner.os }}-nextjs-${{ hashFiles('/package-lock.json', '/yarn.lock') }}-${{ hashFiles('.[jt]s', '.[jt]sx') }}
# If source files changed but packages didn't, rebuild from a prior cache.
restore-keys: |
${{ runner.os }}-nextjs-${{ hashFiles('/package-lock.json', '/yarn.lock') }}-
- name: Install dependencies
run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
- name: Build with Next.js
run: ${{ steps.detect-package-manager.outputs.runner }} next build
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: ./dist

Deployment job

deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4`

oguzalpakgul Feb 10, 2024

I had the same error. it was fixed when I put the following line in the comment line.

- name: Setup Pages
uses: actions/configure-pages@v4
with:
# Automatically inject basePath in your Next.js configuration file and disable
# server side image optimization (https://nextjs.org/docs/api-reference/next/image#unoptimized).
static_site_generator: next

The last part path: ./dist is the file name at the output point. If you run npm run build on your computer and it outputs to the "./out" file, you need to put path: ./out in the path.

Mgphone · 2024-02-21T07:30:15Z

Mgphone
Feb 21, 2024

`# Sample workflow for building and deploying a Next.js site to GitHub Pages
#
# To get started with Next.js see: https://nextjs.org/docs/getting-started
#
name: Deploy Next.js site to Pages

on:

#Runs on pushes targeting the default branch
push:
branches: ["main"]

#Allows you to run this workflow manually from the Actions tab
workflow_dispatch:

#Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
contents: read
pages: write
id-token: write

#Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
#However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
group: "pages"
cancel-in-progress: false

jobs:

#Build job
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Detect package manager
id: detect-package-manager
run: |
if [ -f "${{ github.workspace }}/yarn.lock" ]; then
echo "manager=yarn" >> $GITHUB_OUTPUT
echo "command=install" >> $GITHUB_OUTPUT
echo "runner=yarn" >> $GITHUB_OUTPUT
exit 0
elif [ -f "${{ github.workspace }}/package.json" ]; then
echo "manager=npm" >> $GITHUB_OUTPUT
echo "command=ci" >> $GITHUB_OUTPUT
echo "runner=npx --no-install" >> $GITHUB_OUTPUT
exit 0
else
echo "Unable to determine package manager"
exit 1
fi
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: "20"
cache: ${{ steps.detect-package-manager.outputs.manager }}
- name: Setup Pages
uses: actions/configure-pages@v4
with:
# Automatically inject basePath in your Next.js configuration file and disable
# server side image optimization (https://nextjs.org/docs/api-reference/next/image#unoptimized).
#
# You may remove this line if you want to manage the configuration yourself.
static_site_generator: next
- name: Restore cache
uses: actions/cache@v3
with:
path: |
.next/cache
# Generate a new cache whenever packages or source files change.
key: ${{ runner.os }}-nextjs-${{ hashFiles('/package-lock.json', '/yarn.lock') }}-${{ hashFiles('.[jt]s', '.[jt]sx') }}
# If source files changed but packages didn't, rebuild from a prior cache.
restore-keys: |
${{ runner.os }}-nextjs-${{ hashFiles('/package-lock.json', '/yarn.lock') }}-
- name: Install dependencies
run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
- name: Build with Next.js
run: ${{ steps.detect-package-manager.outputs.runner }} next build
- name: Upload artifact
uses: actions/upload-pages-artifact@v2
with:
path: ./dist

#Deployment job
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v3`

i still got an error of

1 reply

bensontrent Aug 22, 2024

Remove next export from your package.json then update your next.config file with the export option as described here: https://nextjs.org/docs/app/building-your-application/deploying/static-exports

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The "next export" command has been removed in favor of "output: export" in next.config.js #58790

{{title}}

Replies: 4 comments 23 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

The "next export" command has been removed in favor of "output: export" in next.config.js #58790

Summary

Additional information

Example

Replies: 4 comments · 23 replies

LuciferDIot Dec 5, 2023 Author

To get started with Next.js see: https://nextjs.org/docs/getting-started

Runs on pushes targeting the default branch

Allows you to run this workflow manually from the Actions tab

Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages

Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.

However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.

Build job

Deployment job

To get started with Next.js see: https://nextjs.org/docs/getting-started

Runs on pushes targeting the default branch

Allows you to run this workflow manually from the Actions tab

Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages

Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.

However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.

Build job

Deployment job

Replies: 4 comments 23 replies

LuciferDIot Dec 5, 2023
Author