Declan

@diegohaz Ah yeah, that was the big road block I ran into as well. Everything was working, but it was still just creating 1 chunk because every component/container was being...

Ah yeah, I took at the differences [here](https://github.com/diegohaz/arc/tree/0b9cacb2767a77ac4ea55f0a8c8c5b6c757ebac0/src/components) that you linked in that issue. Those changes look good; it would be slightly more annoying to create your own components but...

Yeah, but I think the biggest pain point with the structure you posted is that you have to remember to add the export to that folder's index file. I only...

@zentuit Wouldn't you potentially end up with a longer initial load? Since the site wide chunk could end up including a lot of unnecessary components? In `arc` for example, you...

@rolele The problem I was referring to was not really the same as this. What I was trying to achieve was to be able to do `import { Atom }...

@rolele Yep exactly, if you use just 1 component and check your chunks you'll see that it includes every component

@advance512 Am I correct in assuming it's an automated way of doing this below? https://github.com/diegohaz/arc/blob/0b9cacb2767a77ac4ea55f0a8c8c5b6c757ebac0/src/components/index.js Could be useful in making generating the above file automated and easy, but maybe it...

@advance512 Out of curiosity did you try to implement something like the above?

@diegohaz You're using a library for this `generate-index`? Just asking as I couldn't find it

Ah ok, makes sense. I suppose some of the code from the current `index.js` file could be re-used to create the logic for generating all the import statements.