Open kevzettler opened 1 year ago
Next export is not yet available/supported for appDir in next 13 as far as I know. You can track the status on the roadmap page: here
Damn. I really need this feature. This is a blocker on my app :/
Yeah this is a bummer I wouldn't have used the latest version had I know this was broken. Now I guess I'll port to an earlier version and by the time I migrate I assume export
will probably be available in the appDir support
You don't have to port to the older version. You can stay on 13. Just don't use appDir. That way you get all the other improvements of v13.
You don't have to port to the older version. You can stay on 13. Just don't use appDir. That way you get all the other improvements of v13.
That's fair; I've just already put ~150 hours into structuring my app around functional async server side components, which I can't use in pages/
This is actually the only problem I've encountered so far that seems too in-the-weeds of the build process for me to address. I'll just cross my fingers for a workaround soon 🤞
Hello there!
FYI - Seems to be it's supported now: https://github.com/vercel/next.js/pull/47022
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
App directory (appDir: true), Static HTML Export (next export)
Link to the code that reproduces this issue
https://github.com/kevzettler/bad-nextjs-export-bug
To Reproduce
npm install && next build && next export
Describe the Bug
next export
fails with the followingExpected Behavior
More clarity in the error message. What is actually missing? The file
app/about/page.tsx
exists and renders innext dev
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response