Concepts - Bundle vs Chunk

[zzzgit]

There is no definite definitions for the concepts bundle and chunk in the documentation of both V1 and V2.
After a learning for several days, I found that they guys use bundle and chunk in the documentation alternately. As if there isn't a clear difference between bundle and chunk.
Am I right?
If not, the effort for documentation improvement is needed.
If it is, I have two suggests:

1. use chunk instead of bundle everywhere, to avoid confusing
2. use chunk as a noun while bundle as a verb

[skipjack]

I have also grappled with this in the past and came to about the same conclusion. It might be tough to enforce one or the other now as there are so many instances of chunk and bundle across this site and elsewhere.

@TheLarkInn maybe a glossary section somewhere under Documentation would be useful at some point?

[rouzbeh84]

I think this is a good idea! I know it may sound easy to search for such terms but for those unfamiliar or new an easy index of all the keywords/domain specific words used around the web and this site itself could be useful to have if not just to link back to within posts on an automated path to hotlink the words during build process?

I went ahead and started one with a few words but didn't get too far just in case it's not wanted by many haha. here is a screen of the glossary branch I've begun. It links all words to their respective pages with more detail.

Thoughts?

[skipjack]

@rouzbeh84 I really like this idea and I think adding it under /content/glossary.md is perfect as it doesn't really fit it any particular section. Aside from linking to it throughout other pages, I'm not sure where the main link would be (e.g. banner, sidebar, footer). I think maybe the footer would be best but maybe we should remove/move some of those other links. Our content is definitely starting to overflow our layout 😭 but were working on that in #438 and #1153.

Feel free to PR whenever though, and close this issue (just make sure to include Bundle and Chunk definitions 😉 ).

[rouzbeh84]

@skipjack it could be hot-linked throughout the docs and possibly the last item on the left list for easy access while going throughout?

Would it be possible to do add some sort of grepping to the build process that generates all used words on the section and put them in a dropdown style link in the left nav like how most sections are populated now?

[skipjack]

it could be hot-linked throughout the docs and possibly the last item on the left list for easy access while going throughout?

Yeah, I was thinking about the bottom of the sidebar as well. That may be a good fit.

Would it be possible to do add some sort of grepping to the build process that generates all used words on the section and put them in a dropdown style link in the left nav like how most sections are populated now?

Anything's possible 😆 ... I'm a little confused as to what you mean by adding it to the sidebar. Maybe you can show me an example? I think what would be really cool is if we grep-ed them as you said and then highlighted them as key terms (maybe with a hover behavior showing the definition).

Let's keep it simple for now and revisit that second part (grep-ing / highlighting / extracting) down the road. I want to avoid adding any more major features/complexity to the site for the time being until we get the issue count down and have some time to clean things up. Here's the roadmap I have in my head...

Knock down remaining issue count (aka get content into a good place) =>
Review and clean up content (grammatical errors, simplification, etc.) =>
Clean up infrastructure/setup (markdown.js 😞 , build/testing setup, etc.) =>
Revisit some of the things we passed over earlier (like step 2 here) and add new features

Doesn't have to be exactly synchronous like that, in fact @bebraw and I are working on a few non-content-related things currently, but I think in general that should be the plan.

[rouzbeh84]

@skipjack

I'm a little confused as to what you mean by adding it to the sidebar. Maybe you can show me an example?

Sorry if I was unclear about the sidebar. I think we're on the same page as I basically meant adding the collected glossary values of current page to a nested list at the bottom like the other sections have. Possibly with a border above to denote it's a type of constant navigation feature? Probably not needed but this type of thing image of sidebar

I think what would be really cool is if we grep-ed them as you said and then highlighted them as key terms (maybe with a hover behavior showing the definition).

This would be really cool!

Let's keep it simple for now and revisit that second part (grep-ing / highlighting / extracting) down the road. I want to avoid adding any more major features/complexity to the site for the time being until we get the issue count down and have some time to clean things up. Here's the roadmap I have in my head...

For sure! I know I'm not too familiar with the build process of this site so just spitballing but will keep it simple for now to get something up and see if it's useful in the first place before altering any build steps.

[skipjack]

I know I'm not too familiar with the build process of this site so just spitballing but will keep it simple for now to get something up and see if it's useful in the first place before altering any build steps.

Yeah, no worries... I think it would fit in somewhere in the markdown processing but let's just get the page up and loop back to this down the road once the markdown.js file has been reworked into something else or cleaned up significantly. It's already been causing a fair amount of issues like #1187, #178 and probably a few others we don't yet know about.

Let's just start by getting that page up, and maybe linking to it from a few places. Ping me once you have something ready for review.

[dwiyatci]

Nice to find this thread! 😃

I have also grappled with this in the past and came to about the same conclusion.

@skipjack So they are actually the same, then? I've also been silently questioning this concept for the past 2 years and used to think that bundle is a collection of chunks ... 😅

[skipjack]

@skipjack So they are actually the same, then? I've also been silently questioning this concept for the past 2 years and used to think that bundle is a collection of chunks...

@dwiyatci Yes I believe they are the same. I had initially thought that "chunks" were analogous with child bundles (similar to your thought that "a bundle is a collection of chunks") but I've also heard the term "entry chunk" used which kind of voids that thought. I'm not an expert though, I would leave the final say to someone from the @webpack/core-team.

[rouzbeh84]

gonna watch this deep dive into code splitting: under the hood by @TheLarkInn and after understanding will add to glossary.

In the meantime, according to survivejs

• Bundle is the result of bundling. Bundling involves processing the source material of the application into a final bundle that is ready to use. A bundler can generate more than one bundle.
  ...
• Chunk is a webpack-specific term that is used internally to manage the bundling process. Webpack composes bundles out of chunks, and there are several types of those.

[skipjack]

@rouzbeh84 you should feel free to pr this page whenever. We can always do follow ups to add and clean up content, doesn't have to be perfect on the first pass.

[dwiyatci]

Ähmm.., sounds to me the @survivejs definition goes more to a direction of bundle ≈ asset 🙃