When making a large application it is best practice to lazy load components as needed. It seems there is no way to lazy load a route in wasp?
route AnotherRoute { path: "/test", to: AnotherRoute }page AnotherRoute { component: import { AnotherRoute} from "@src/client/AnotherRoute",}
route AnotherRoute { path: "/test", to: AnotherRoute }page AnotherRoute { component: import { AnotherRoute} from "@src/client/AnotherRoute",}
I have this route definition. It is in the JS bundle even though I have never navigated to it. This would be an issue as the application grows in size, when a user navigates to the landing page, they will need to download the ENTIRE app.
Does WASP have a way to lazy load components using the build in routing?
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.