-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve docs for next export
#1202
Comments
I got the same error and switched image optimization off. |
Same error as OP. Playing with next config and various solutions, but I suspect something isn't parsing between nextConfig and withNextra() on export. @pplonski can you share your working config? Thanks! |
I just used: // next.config.js
const withNextra = require("nextra")({
theme: "nextra-theme-docs",
themeConfig: "./theme.config.jsx",
});
module.exports = {
...withNextra(),
images: {
unoptimized: true,
},
}; From what I read the |
Working for me on non-Vercel & Vercel deploys:
const withNextra = require('nextra')(https://github.com/shuding/nextratheme-blog', './theme.config.js')
const nextConfig = {
images: {
loader: 'akamai',
path: '/'
}
}
module.exports = withNextra(nextConfig)
|
Discussed in #1197
Originally posted by RPDeshaies January 6, 2023
Hi, I'm currently testing using Nextra in replacement for a Vuepress project I had and I was wondering if it was possible to use the command
next build && next export
with Nextra?I've tried running the command and looking at the exported assets, but I'm getting a bunch of 404 of the static assets (js/css/etc)
I initially had an error about using next/images which I fixed by overriding a config in the next config, but I'm not sure at all that's the proper way of doing things.
Thanks in advance for the help. And also, Nextra looks absolutely fantastic, I'm really eager to make it work!
The text was updated successfully, but these errors were encountered: