Can elm-pages-v3 help with compile times for large CRUD applications?

Does elm-pages-v3 create one elm app per page? If so, can it help keep compile times (and compiler memory usage) constant as the number of pages grows?

My understanding is that it creates one elm app that all pages use. It then doesn’t require a reloading the app (just a data fetch) when switching pages.

1 Like

No, elm-pages doesn’t create one Elm app per page. It brings JAMstack concept tooling to Elm. As far as Elm compilation scaling goes, it will be the same as any Elm project.

Do you have an existing compile time / memory usage issue? I’m curious about the details of that if so.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.