A "next dev" option/mode, to compile all pages at once

[nicolaslima321]

Goals

1. Have an option/flag to next dev, that compiles all the pages, inside the app directory, at once, instead of compiling on each request. This could be something like next dev --compile-all-pages for example.

Non-Goals

1. Restrict the NextJs development, to compile the components only in a kind of route/request demand 😕.

Background

This feature is needed, because at least by me.. I'm having a very bad developer experience, when I need to navigate in many, or more than one pages in my application.
I understand the reasons, but, whats the matter on provide an option to compile all the pages? Some developers may prefer to wait until all the pages compile only once, instead of wait on the compile every single time.

Proposal

Maybe implement a flag to next dev understand that it's supposed to compile all the pages

[nicolaslima321]

this feature request comes from the follow issue #6554

[FrenchMajesty]

I agree. This is much needed. I am new to the NextJS but the next dev is so unusable I am actually baffled that startups are building with this?!

It takes 10sec for me to transition from one page to the next.

[sgoodrow]

A hybrid option would be nice. Compile pages as fast as possible, starting with those requested by the client.

[jordanbtucker]

I just ran into a different use case for this feature.

I'm prototyping some REST calls using a mock app/notes/db.ts file. In that file, I have a NOTES array that mocks a DB collection and a few functions for reading and manipulating that array (getNotes, createNote, etc.).

Then, I have an app/notes/route.ts file with a GET and POST function, and an app/notes/[id]/route.ts file with a GET and PUT function, and they both call the mock DB functions. If I send a GET or POST request to /notes, the NOTES array is initialized on the fly, which is fine. But the first time I make a GET or PUT request to /notes/1, it compiles app/notes/[id]/route.ts and the array is reinitialized, so any notes I created before that are gone.

Obviously, this interferes with mocking my rest calls. Sure, I'll eventually be using tests, but I'm just prototyping right now, and it's frustrating that I have to make a request to both /notes and /notes/1 before I can make any requests that don't reinitialize my mock DB. I'm used to my mock data being reinitialized after changing a file, but not in the middle of testing.

Maybe I'm missing something.

[CodeGeek04]

I agree, we need some kind of option in dev script to atleast specify the pages to be compiled beforehand, if not all of them.

[MathiasOxholm]

Agree with this one. I'm currently running Playwright with the dev server, and navigating between pages causes timeouts from Playwright's side. Bumping the timeout fixes it sort of, but would be nice not to have this issue at all.

[timmypidashev]

This would be very nice. Currently struggling with some pretty annoying issues like caddy giving a 502 because my next-auth page doesnt compile fast enough in dev mode. A feature flag to precompile in dev mode would be very neat and highly appreciated 👍

[andrewmartin]

I'd love this as well.

I wonder if there's some weird or hacky way to do this using old fashioned curl and a combination of useSelectedLayoutSegments. Idea would be to write a script that:

1. prints out all of the registered routes
2. then runs curl -XGET on all of them

Definitely hacky, but might get the job done?

[okunamayanad]

I'd love to see this. Currently, I just hit all the pages when I restart the dev server but this is not optimal for DX. I have a beefy CPU so I'd like an option to just compile all pages in the background