Replies: 8 comments 17 replies
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
|
Seems to break with the latest version of nextjs 13.0.3. Getting an internal server error 500. @ascorbic should we continue to use the next js runtime at 4.29.1 or should we lock to 4.28.4-appdir.0 for now? |
Beta Was this translation helpful? Give feedback.
-
|
I will be putting a new version of the appdir branch out tomorrow |
Beta Was this translation helpful? Give feedback.
-
|
@ascorbic thanks! Appreciate it :) |
Beta Was this translation helpful? Give feedback.
-
|
@ascorbic QQ is there anyway to have the runtime auto upgrade only to the appDir versions (I know one usually uses |
Beta Was this translation helpful? Give feedback.
-
|
If you explicitly set the dependency to |
Beta Was this translation helpful? Give feedback.
-
|
Hello guys |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I am also having the same issue occur, excited for this patch! |
Beta Was this translation helpful? Give feedback.
-
|
I too seem to be having the same issue |
Beta Was this translation helpful? Give feedback.
-
|
I’m also seeing the same issue of complete page re-renders when navigating with the component. Looking forward for a fix as well! |
Beta Was this translation helpful? Give feedback.
-
|
Just tried the app on Vercel, and seems to be fine. So it does at least appear to be related to Netlify in particular. |
Beta Was this translation helpful? Give feedback.
-
|
Any update to fix this behaviour? |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if this is a Netlify issue or a problem with my own code, but I keep getting a 500 Internal Server error when trying to |
Beta Was this translation helpful? Give feedback.
-
|
Hi. I've replied on SO, but looking at your logs you're getting the error "Error: Page changed from static to dynamic at runtime /team/1, see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error" |
Beta Was this translation helpful? Give feedback.
-
|
This solved my issue. Thank you so much for the tips! |
Beta Was this translation helpful? Give feedback.
-
|
It seems that Next.js 13's loading UI doesn't work with Netlify (i.e. React Suspense component.) My suspense component works fine locally with
|
Beta Was this translation helpful? Give feedback.
-
|
I'll take a look, thanks. Could be because we don't support streaming from the Node runtime? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Sounds like a reasonable hypothesis, but a bit over my pay grade at this time. |
Beta Was this translation helpful? Give feedback.
-
|
I have noticed this issue as well. Commenting to hopefully stay in the loop. Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Someone using appDir and trailingSlash with nextjs@13.1.6? Opening the url www.example.com/blog/article-a/ results in a redirect to www.example.com/blog/article-a I've also deployed the same site to vercel and there trailingSlash is respected. I get no redirect. Is this a known issue? |
Beta Was this translation helpful? Give feedback.
-
|
Issue: 500 Internal Server Error when deploying Next 13.4 with embed sanity studio on Netlify. Adding an embed Sanity studio on Next 13.4. causes "500: Internal Server Error". The problem seems to be specifically related to the serverActions in Next.js 13.4, as the application works fine locally and on previous versions (e.g., 13.3) on the production. Here is the log on Netlify Functions:
As a temporary workaround, setting the environment variable "__NEXT_PRIVATE_PREBUNDLED_REACT=next" resolved the issue for others. However, Netlify does not allow this particular environment variable to be set due to the prefix of (_). During investigation, I came across a discussion thread in the Netlify Support Forums that addresses a similar error: Netlify Support Forums Thread. Additionally, I noticed that there is a pull request in the Next.js GitHub repository that appears to address similar issue specifically for custom servers. It seems to have been fixed and merged on v13.4.0 but many others as well as I'm still getting the error. This might just be an issue with Next itself. Just wanted to point it for someone from Netlify to look into. Next.js PR. |
Beta Was this translation helpful? Give feedback.
-
|
@sadhikari1r, we're currently upgrading to 13.4 in the Next.js runtime. You can follow along here, #2080 |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I am trying to deploy a next 13 app using 'app' router to Netlify. I added a 'not-found.js' to the 'app' directory to create my custom 404 page so that it will be shown when user visit any invalid URL . I tried to create a repo for testing with just the starter file (npx create-next-app@latest). Without 'not-found.js', the Next default 404 page would be shown when I went to an invalid URL (https://647825f32dfd7e319f25f51d--regal-pika-910873.netlify.app/unkown): However, when I added the 'not-found.js' to 'app' directory and visited an invalid URL, the custom 404 page could not be shown. Instead, "Internal Server Error" was shown (https://647826e083bb9900089436a2--regal-pika-910873.netlify.app/unkown): I have also tried to deploy a next app using 'page' router and added '404.js' to 'page' directory and it works well(https://amazing-quokka-cb8229.netlify.app/unknown): Is there any solution if I would like creating my custom page with 'app' directory? Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
When deploying a Next.js 13.4.4 app to Netlify I had some issues. At first I thought the deployment worked but I got the Netlify 404 page when I went to the site's URL. In Netlify the build was not executed, only the post-processing stage was executed. For it to work I just had to add the following to a For full context my stages:
- build
- deploy
build-app:
stage: build
image: node:16
script:
- npm install
- npm run build
artifacts:
paths:
- .next/
netlify:
stage: deploy
image: node:16
script:
- npm install -g netlify-cli
- netlify deploy --site $NETLIFY_SITE_ID --auth $NETLIFY_AUTH_TOKEN --build --prod --dir=.next
only:
- main |
Beta Was this translation helpful? Give feedback.
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
If you update your site to Next 13, it will work on Netlify right away. All the stable features work out of the box with no changes required on your part when using the latest Netlify Next.js runtime. If you have manually installed the Netlify Next.js runtime in your package.json you will need to upgrade it, but for everyone else it will upgrade you automatically on your next deploy. However this does not include the new experimental
appdirectory features. This is currently pre-release and should not be used for production.While deploying
appdirectory sites to Netlify is still experimental, it already supports many of the most interesting new features, including React Server Components and streaming HTML using the edge runtime. Pages that use the edge runtime are automatically deployed to Netlify Edge Functions.This topic is for discussion of the use of
appdirectory features, not general Next 13 topics. If you encounter a problem with an existing feature such as thepagesdirectory or middleware, then open an issue rather than commenting here.Update: you no longer need to install a special version of the runtime - the auto-installed version has appDir support enabled, though it is still experimental
Known issues
next.config.jsto rewrite to a page that uses the edge runtime. The workaround is to use middleware to rewrite, which works correctly."missing"middleware matcher #1796Beta Was this translation helpful? Give feedback.
All reactions