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?

Hello guys 👋
So, I'm trying to deploy my NextJS 13 test app to Netlify (of course using appdir experimental feature) and weirdly enough all my routes navigation is turned into a hard page refresh 🤔 Is that expected?
Here is the preview of the app.
If you click on "Hello" text it should redirect you to the hello page using a hard page refresh.

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 fetch() data. I've described my issue in detail on StackOverflow.

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 npm run dev and ntl dev, but it doesn't work when deployed to Netlify. One clear way to see this is by using the React developer tools Chrome extension.

ntl dev
Screenshot 2023年01月26日 at 3 50 05 PM

https://loading--dundermifflininc.netlify.app/team
Screenshot 2023年01月26日 at 3 50 39 PM

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?

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:

May 9, 12:02:35 PM: c0984344 ERROR Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './server.edge' is not defined by "exports" in /var/task/node_modules/react-dom/package.jsonMay 9, 12:02:35 PM: c0984344 ERROR at new NodeError (node:internal/errors:387:5)May 9, 12:02:35 PM: c0984344 ERROR at throwExportsNotFound (node:internal/modules/esm/resolve:365:9)May 9, 12:02:35 PM: c0984344 ERROR at packageExportsResolve (node:internal/modules/esm/resolve:649:3)May 9, 12:02:35 PM: c0984344 ERROR at resolveExports (node:internal/modules/cjs/loader:554:36)May 9, 12:02:35 PM: c0984344 ERROR at Function.Module._findPath (node:internal/modules/cjs/loader:594:31)May 9, 12:02:35 PM: c0984344 ERROR at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1012:27)May 9, 12:02:35 PM: c0984344 ERROR at /var/task/node_modules/next/dist/server/require-hook.js:180:36May 9, 12:02:35 PM: c0984344 ERROR at Function.Module._load (node:internal/modules/cjs/loader:871:27)May 9, 12:02:35 PM: c0984344 ERROR at Module.require (node:internal/modules/cjs/loader:1098:19)May 9, 12:02:35 PM: c0984344 ERROR at require (node:internal/modules/cjs/helpers:108:18) {May 9, 12:02:35 PM: c0984344 ERROR code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'May 9, 12:02:35 PM: c0984344 ERROR }

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.

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):
image

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):
image

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):
image

Is there any solution if I would like creating my custom page with 'app' directory? Thank you.

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.
image

For it to work I just had to add the following to a netlify.toml file in the root of the repo.

[build]
 publish = ".next"

For full context my .gitlab-ci.yml file looks like this.

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

Hi! Dynamic routes (generated from mdx files) do not work with netlify form actions.
If such routes are used in the form action field, it results in a timeout:
CleanShot 2023年06月16日 at 22 34 07@2x

The form submit works if the same page is created (as a directory under the app).

Hi there.

I just tested out some changes on a preview deployment and the serverless function seems to be crashing and I have no idea why.

Jun 21, 03:59:26 PM: 2023年06月21日T13:59:26.108Z	undefined	ERROR	Uncaught Exception 	{"errorType":"Error","errorMessage":"Could not find Next.js server","stack":["Error: Could not find Next.js server"," at Object.<anonymous> (/var/task/apps/bikeworld/.netlify/functions-internal/___netlify-handler/___netlify-handler.js:2:9)"," at Module._compile (node:internal/modules/cjs/loader:1196:14)"," at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)"," at Module.load (node:internal/modules/cjs/loader:1074:32)"," at Function.Module._load (node:internal/modules/cjs/loader:909:12)"," at Module.require (node:internal/modules/cjs/loader:1098:19)"," at require (node:internal/modules/cjs/helpers:108:18)"," at Object.<anonymous> (/var/task/___netlify-handler.js:1:18)"," at Module._compile (node:internal/modules/cjs/loader:1196:14)"," at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)"]}

https://14-134258--bikeworldmvp.netlify.app/.netlify/functions/___netlify-handler

What more information do you need to help me figure out why this is happening?

instead of showing 404 its showing me this
screencapture-hr-houze-netlify-app-refund-2023年06月26日-05_10_44

Same issue of page reloading with app routing

Got error 500 when refreshing a shop/[bundleId] page on this minimal reproduction repo: https://github.com/DWboutin/test-routing

Static Images wont load on Netlify when they load on Vercel properly

Updated Next.js to last version 13.5.2, it is fixed.🚀

I am trying to deploy Next.js 13.5.2 App but still get the following:

image

I am using the app router and tried to deploy with GitLab integration. In the deploy logs in Netlify everything was "green" and complete.

Does anybody know if dynamicParams still is not supported?