[Breaking] NextJs [14.2.3] Draft mode with static pages about next.js HOT 6 OPEN

@jizhi0v0 I understand what you are trying to say. However, I need the page to be static not dynamic.

However, the default behavior for Static pages during Draft mode is Dynamic
https://nextjs.org/docs/app/building-your-application/configuring/draft-mode

Draft mode is usually used when you work with CMS so the admin will have the ability to change static pages and view the changes in real time instead of requiring rebuilds or invalidate the cache on change. ( so the page will be dynamic during that time only)

from next.js.

I have created another issue #66282 for the MaxListenersExceededWarning.

from next.js.

Add "use client" at the top of /home/page.tsx.

from next.js.

@jizhi0v0 adding "use client" makes the page client side. The Idea here is to use static page, so it should stay server side.

There is a huge change of behavior between versions which is not announced in the blogs. Which means it is unexpected behavior ( a bug ) that occurred.

from next.js.

@jizhi0v0 adding "use client" makes the page client side. The Idea here is to use static page, so it should stay server side.

There is a huge change of behavior between versions which is not announced in the blogs. Which means it is unexpected behavior ( a bug ) that occurred.

Add "use client" or switch to 'force-dynamic'.I don't know if what I said is correct, I hope it can help you

https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config

'force-dynamic': Force dynamic rendering, which will result in routes being rendered for each user at request time. This option is equivalent to getServerSideProps() in the pages directory.

from next.js.

I am experiencing a similar issue after upgrading Next.js from 14.0 to 14.2.3, with the difference that we are not using draft mode, but we are using server side generated pages fetching content from a CMS using Apollo client. The server will not stop when I use ctrl + c and the memory limit warning is displayed. This is when using next build then next start. The issue does not occur when running next dev.

from next.js.