Is it really multi-page if all pages have to share the same config?

[robvon]

I would like an example where an initial config is loaded, containing 'aspect-oriented' stuff and maybe some jQuery lovelyness. If there is a constant landing page it could include that too.

Then as a page is dynamically loaded, one can dynamically update the dependencies for modules on that page. As a page is loaded, a function that calls require.config would be expected (pseudo interface) to exist like the 'init' in shims.

This will also allow teams to develop 'pages' without having to modify the shared config when a new page is added or as in my case, a third party to develop all the views whilst I do the data api. We have nothing in common except jQuery which I preload then fake the define to keep it out of the config.