You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started writing the Concepts section modeled after some of the talks I had done at conferences prior to. It featured talking about key concepts vs configuration properties that I felt people should be aware of.
GOAL: Give people a clear super-high level overview of how webpack works by teaching them the 4 main pieces that one might use in their configuration. This should give people enough confidence to run with it, understand how to use any loader or any plugin, or leverage any entry or output properties with basic usage.
With that in mind, I'm really happy to have you gauge if you feel we are lacking or needing more information. It is admittedly hard for me to tell whether or not the information is enough to leave people confident.
@TheLarkInn would you say the Concepts section is targeted at people who possibly have not used a bundler before? If so I have some re-wording suggestions that I'll do PRs for.
Yes!! Not only no bundlers, but no understanding of a js module. I picture me circa 2 years ago never seeing module.exports and export default and how grunt just concatenates stuff together.
The concepts section has been reorganized several times since this was opened in 2017 and now has a defined set of pages (Entry Points, Output, Loaders, Plugins, Configuration, Modules, Module Resolution, Module Federation, Targets, Manifest, Under the Hood, Why webpack). Closing this open-ended review; specific gaps are better tracked as their own issues.
Activity
TheLarkInn commentedon Jul 11, 2017
I'll start with the goal(s):
I started writing the Concepts section modeled after some of the talks I had done at conferences prior to. It featured talking about key concepts vs configuration properties that I felt people should be aware of.
GOAL: Give people a clear super-high level overview of how webpack works by teaching them the 4 main pieces that one might use in their configuration. This should give people enough confidence to run with it, understand how to use any loader or any plugin, or leverage any entry or output properties with basic usage.
With that in mind, I'm really happy to have you gauge if you feel we are lacking or needing more information. It is admittedly hard for me to tell whether or not the information is enough to leave people confident.
tanyagray commentedon Jul 12, 2017
@TheLarkInn would you say the Concepts section is targeted at people who possibly have not used a bundler before? If so I have some re-wording suggestions that I'll do PRs for.
TheLarkInn commentedon Jul 12, 2017
Yes!! Not only no bundlers, but no understanding of a js module. I picture me circa 2 years ago never seeing module.exports and export default and how grunt just concatenates stuff together.
TheLarkInn commentedon Jul 12, 2017
Are you wanting to do in one pass or document issues, then that way we can track it? Take step by step etc.
shaodahong commentedon Jul 12, 2017
@TheLarkInn Webpack base on module, but if no understanding of module, should be suggust to study module, Is this mean?
tanyagray commentedon Jul 12, 2017
Documenting issues is a good idea. Will do.
TheLarkInn commentedon Jul 16, 2017
Awesome I just saw that! It's a a great audit. Do you want to tie it to this one?
docs(guides): add build-performance page (#1506)
TheDutchCoder commentedon Oct 26, 2017
Currently working on #1416 with PR #1673
Thanks for bringing this to our attention @tanyagray 👍
alexander-akait commentedon Sep 11, 2026
The concepts section has been reorganized several times since this was opened in 2017 and now has a defined set of pages (Entry Points, Output, Loaders, Plugins, Configuration, Modules, Module Resolution, Module Federation, Targets, Manifest, Under the Hood, Why webpack). Closing this open-ended review; specific gaps are better tracked as their own issues.
Generated by Claude Code