Skip to content

Update why-webpack.md #2630

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 5, 2018
Merged

Update why-webpack.md #2630

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8c9a30a
Update why-webpack.md
Stef733 Oct 31, 2018
505b3fe
Merge branch 'master' into patch-1
Stef733 Nov 3, 2018
e15cec4
Merge branch 'master' into patch-1
Stef733 Nov 4, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/concepts/why-webpack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ contributors:
- EugeneHlushko
---

To understand why you should use webpack lets do a recap of how we use JavaScript on the web before bundlers were a thing.
To understand why you should use webpack let's do a recap of how we use JavaScript on the web before bundlers were a thing.

There are two ways to run JavaScript in a browser. First, include a script for each functionality you want to implement, the issue is that the solution is hard to scale as loading too many scripts causes a network bottleneck. The other alternative is to load a big .js file containing all your project code, but this results in an unmaintainable scripts that causes problems in scope, size, readability, fragility and monolith files.

Expand Down