webpack-rails-react 1.0.3 → 1.0.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +3 -0
- data/example/boilerplate/router/application.js +2 -2
- data/lib/webpack/rails/react/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: e648ebd9ed9c65d4f05cae99788cb61f18119f71
|
4
|
+
data.tar.gz: 6d8dfdd8823dabe0035be121f0a8e4a3cdd259fb
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 70c31b7ce725105199be5e2766f1b11ea4866c8026baf970b52be2f599279b56f5fcea946c8fa8e4e9f36d3bc5abf5128c23716ce4ddb9f74c25e581eca2c57f
|
7
|
+
data.tar.gz: 1a4f23c436e1f4f501284c5c6d359f627f628bb0c2fbb96f0325a7474645f4a42936678226a5abea2ee9d471eed9cabd139063b66707485ee9ff850231565f23
|
data/README.md
CHANGED
@@ -69,6 +69,9 @@ Add `rake webpack:compile` to your deployment. It serves a similar purpose as Sp
|
|
69
69
|
|
70
70
|
If you're using `[chunkhash]` in your build asset filenames (which you should be, if you want to cache them in production), you'll need to persist built assets between deployments. Consider in-flight requests at the time of deployment: they'll receive paths based on the old `manifest.json`, not the new one.
|
71
71
|
|
72
|
+
## Example Apps
|
73
|
+
[basic](https://github.com/wdjungst/webpack-rails-react-basic)
|
74
|
+
[react-router](https://github.com/wdjungst/webpack-rails-react-router)
|
72
75
|
## TODO
|
73
76
|
|
74
77
|
* Add eslint to client
|
@@ -4,7 +4,7 @@ import { Router, browserHistory } from 'react-router';
|
|
4
4
|
import routes from './routes';
|
5
5
|
|
6
6
|
ReactDOM.render(
|
7
|
-
<Router history={
|
8
|
-
|
7
|
+
<Router history={browserHistory} routes={routes} />,
|
8
|
+
document.getElementById('app')
|
9
9
|
);
|
10
10
|
|