Skip to content

Commit 34b4e54

Browse files
committed
Update README.md
1 parent 6df85ba commit 34b4e54

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

README.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ to the following articles from http://spapas.github.io/:
88
- http://spapas.github.io/2015/07/02/comprehensive-react-flux-tutorial-2/
99
- http://spapas.github.io/2015/09/08/more-complex-react-flux-example/
1010

11-
To be able to follow the articles, I've added a bunch of tags in the repository(they go from
11+
To be able to follow the articles, I've added a bunch of tags in the repository (they go from
1212
the simplest case to the most complex one):
1313

1414
- react-only
@@ -42,14 +42,16 @@ Now, to actually run the application, you'll need to use
4242

4343
to start the django development server (or run rs.bat/rs.sh depending on
4444
your shell). For the ``react-only`` version you
45-
can directly modify the js files and see the differences. However, for all
46-
other versions a node-js toolset is used to compile the javascript sources
47-
to a bundle that is actually used.
45+
can directly modify the js files and see the differences when you
46+
refresh the page in your browser. However, for all
47+
other versions a node-js toolset with browserify is used to compile
48+
the javascript sources to the bundle that is actually used.
4849

4950
So, when developing I recommend running ``npm run watch`` to start watchify
5051
which automatically re-builds your javascript bundle when it detects a change. Another
5152
solution is to run ``npm run build`` that will create a (minified) bundle with
52-
the current sources (but will need to be re-run by hand when something changes).
53+
the current sources (but will need to be re-run by hand when something in your
54+
javascript changes).
5355

5456

5557
You can find more info about how I use this node-js toolset

0 commit comments

Comments
 (0)