Is it possible to load full components on the fly as you navigate? #180
Comments
|
I feel worrying about this might be slightly premature - like: please don't try and do this until you run into actual issues with dependency size. that said: yeah you could def get some empty view that displays a placeholder, while it pulls down a new bundle containing a bunch of fresh components. And once the bundle is done loading, it could show the elements. Possibly using some sort of namespaced model to manage the state of loading the bundle. Or perhaps use a But yeah, once again: I wouldn't worry about this too much for now until you've actually built a huge application that needs splitting. Hope this answers your question. Cheers! |
|
As a person who directs and trains developers, I evaluate technology so that I can guide people on what are the best things to use. Having been a professional developer for over 25 years, I already know what types of things corporations run into building large apps. I've seen it over and over again. Corporations are dealing with large complex apps. So my point in bringing this up is that I know this is a requirement for large apps and it would be beneficial to many others as well. This is something that is already available with React and React Router, so I was hoping choo would have an official story on how to handle this. I think choo looks promising as an alternative framework but I need to understand how it scales up to build complex apps. I can't recommend it for large apps unless I know how it can deal with componentization, dynamic loading, ... As the author, given that you are the most familiar with the best way to use this framework, if it is possible to do this type of thing then it would be extremely valuable for you to document or create an example showing how this would work. Anyone that is evaluating the technology will be looking for some key features with examples and in the absence of those, choo might be dismissed prematurely. In Javascript there are just so many frameworks coming out everyday and developers typically don't have the time to just figure this stuff out themselves. They will just go with the ones that clearly support their necessary features and have already documented and created examples. So that's why I posted this issue. I think choo has some real innovation here and I would like to see it succeed. Anything you can do to document, create examples, and think about how this scales up to very large apps the better. No one wants to start using a framework if there is a chance they are going to run into a brick wall down the road, they need to know the strategies available to them as their app grows and becomes complex. All the best. |
|
Ah yeah, fair enough - reopening ✨. If people are curious about this then scribbling down a somewhat more elaborate answer might be good. Hmm, I think this might be a good one for the handbook. I think an elegant solution will probably be possible in the near future, most likely being somewhat a combination of factor-bundle and #155. Thanks heaps for opening this issue; definitely something to consider for people that are planning to build huge things with choo 🚒:train::train::train: |
|
Awesome! That's wonderful. Thanks. On Wed, Jul 20, 2016 at 1:27 PM, Yoshua Wuyts notifications@github.com
Jeff Barczewski |
|
Closing because |
When building large apps, sometimes it is nice to not load all possible components until they are needed, so when a user navigates to a particular route then we dynamically load the components and all their associated parts.
Does choo support the ability to dynamically load components (and their reducers, effects, and subscriptions)?
If so how is this done? Can you point to or create a good example?
The text was updated successfully, but these errors were encountered: