Skip to content

Commit 16f0ab3

Browse files
markfingermarkfinger
committed
Docs
1 parent f1e33b6 commit 16f0ab3

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

‎README.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,10 @@ setup involves a build tool and a python package that can integrate it.
9292

9393
The two most popular build tools are:
9494

95-
- [Webpack](https://webpack.github.io) - can compile your files into browser-executable code and provides a
95+
- [Webpack](https://webpack.github.io) - compiles your files into browser-executable code and provides a
9696
variety of tools and processes which can simplify complicated workflows.
97-
- [Browserify](http://browserify.org/) is another popular tool and has a lot of cross-over with webpack. It
98-
is argurably the easiest of the two to use, but it tends to lag behind webpack in certain functionalities.
97+
- [Browserify](http://browserify.org/) - has a lot of cross-over with webpack. Is argurably the easiest of the
98+
two to use, but it tends to lag behind webpack in functionality.
9999

100100
For React projects, you'll find that webpack is the usual recommendation. Webpack's hot module replacement,
101101
code-splitting, and a wealth of loaders are the features typically cited as being irreplaceable.
@@ -105,10 +105,11 @@ changes to your components to be streamed live into your browser.
105105
To integrate webpack's output into a python system, the two most popular solutions are:
106106

107107
- [django-webpack-loader](https://github.com/owais/django-webpack-loader) - uses a webpack plugin to generate a
108-
file for your python process to consume. Tends to be simpler to reason about, does one thing and does it well.
108+
file for your python process to consume. Tends to be easier to reason about - does one thing and does it well.
109109
Requires you to interact with webpack directly.
110110
- [python-webpack](https://github.com/markfinger/python-webpack) - talks to a build server that wraps around
111-
webpack. Tends to be more complex, but offers more features. Requires you to run a build server.
111+
webpack. Tends to be more complex, but offers more features. Requires you to interact with a webpack-build
112+
process.
112113

113114
For most use-cases, both tools will provide similar functionalities. django-webpack-loader puts you in direct
114115
control of webpack's processes, so it's a good starting point to learn about the tool. python-webpack

0 commit comments

Comments
 (0)