Slow "> Building page:"

In dev mode, Next takes 26+ seconds to build a page for me.

DONE Compiled successfully in 26253ms

This has become a major pain during development, each time I change code.

I presume this is because I have lots of npm packages (48), or they are large/complex.

Do others experience this?

Can anything be done to speed this up, besides removing packages?

[marbemac]

Our two cents - now that we’re fully migrated over to next, we’re seeing issues similar to @chaffeqa - particularly since every page requires most of our JS because of our mobx stores (like what is described above with redux).

In addition, we get the memory fault described in #282 at least a few times a day (much more for team members with less powerful computers).

We moved from base webpack + dll plugin, which did not have any of these issues. There was a longer startup cost (60s), but subsequent pages did not have to rebuild, and we did not run into memory leaks. This is a MUCH nicer dev experience imho, since we only really need to do a cold start once or twice a day, but we’re constantly navigating pages.

Question 1: is there a way to compile all the pages on server start (to disable the on demand page fetching)?

Question 2: If there is anything that we can try to help this situation and speed up our development? DDL plugin sounds promising (and helped us before) - particularly since we load heavy dependencies like https://github.com/codemirror/CodeMirror, https://github.com/jpuri/react-draft-wysiwyg, and https://github.com/Semantic-Org/Semantic-UI-React.

Above complaints aside, thanks for all the hard work that’s been put into next - it’s a fantastic library 😃.

[rauchg]

It’s part of our very near-term roadmap to dramatically speed up compilation performance, both for dev and prod. A big part of that is doing less work.