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
Copy file name to clipboardExpand all lines: src/content/concepts/why-webpack.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ contributors:
8
8
- EugeneHlushko
9
9
---
10
10
11
-
To understand why you should use webpack lets do a recap of how we use JavaScript on the web before bundlers were a thing.
11
+
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.
12
12
13
13
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.
0 commit comments