Split up packages? about aurelia HOT 5 CLOSED

I think the move will likely have negative effect on bundle size, what do you think about it ?

from aurelia.

I'm concerned that this will not only enlarge the bundle size but make it much harder for people to start a new project. We want to have a way to do this without needing npm or a bundler. Single-file script is still something we eventually want.

I'd vote to wait on anything like this for a while. However, I don't see any reason not to do the design work on breaking things into different classes. I think we should consider that independent of how the packages are shipped right now.

from aurelia.

I think the move will likely have negative effect on bundle size, what do you think about it ?

Not that much. There is of course the overhead of the extra class declarations, but most of the logic can still be shared via decorators. Then there will also be a few lines of code less due to certain conditionals that aren't necessary anymore (speaking of observers)

We want to have a way to do this without needing npm or a bundler. Single-file script is still something we eventually want.

We could output multiple bundles for the runtime with packages included/excluded if single file is an important thing. For those who don't need two-way (static / marketing sites, etc) they would have a smaller bundle in the end.

I'd vote to wait on anything like this for a while. However, I don't see any reason not to do the design work on breaking things into different classes. I think we should consider that independent of how the packages are shipped right now.

I was curious what you guys thought about it and I agree. Not something I planned to do soon, but we can keep it in mind with the design. For example by putting the observers in their own folder.

from aurelia.

Sounds good :)

from aurelia.

Closing this since my request for comment has been fulfilled :)

from aurelia.