nextra-docs-template
nextra-docs-template copied to clipboard
shuding
feat: upgrade to Next.js 15 and Nextra 3
Closes: #85, #84, #25
Upgrades the docs template to Next.js v15 and Nextra v3.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| nextra-docs-template | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 23, 2024 5:21pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
If you can provide me with the Vercel logs I can take a closer look at whatever is failing in the deployment. The dev server is successful locally and the docs site builds with pnpm build.
hey @sean-perkins , great work. Just came across your updates. For me locally using your sean-perkins:main branch gave me the following error:
❯ pnpm build
> [email protected] build /Users/johndoe/developer/nextra-docs-template
> next build
(node:20762) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
⨯ Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
> Build error occurred
SyntaxError: Cannot use import statement outside a module
at <unknown> (next.config.js:1)
ELIFECYCLE Command failed with exit code 1.
Checking the docs for nextra and then renaming next.config.js -> next.config.mjs fixed the dev and build. Maybe you want to give this a try and that will also fix the vercel build :)
- node --version:
v20.18.1 - pnpm --version:
9.15.0
@mavogel thanks for the suggestion! Not sure how I overlooked that warning in the terminal.
Enabling ESModules seems to have fixed the preview deployment.
How long do these usually take to be merged? I am facing a new project and considering nextra if it is usable with next.js 15. TIA.
