UI lazy loading useless in Single Page Application


#1

Since in a spa all ui resources will be available client-side on page loaded, still it remains a best practice use imports/ui/ folder for ui components?
(all files in imports/ui/ will be sent, otherwise the file is not necessary)

Or maybe they should be moved into another folder (e.g. client/)?


#2

It might seem useless from a bundling/performance point of view, since the Meteor build tool doesn’t currently support code splitting, tree-shaking, etc., but this is the first step. Code splitting is likely coming soon via reify; leveraging ES2015 modules and lazy evaluation will help make this all possible.