Skip to content

Commit fbda06f

Browse files
shapiromatronowais
authored andcommitted
added changelog (django-webpack#121)
1 parent 083e08c commit fbda06f

File tree

2 files changed

+69
-3
lines changed

2 files changed

+69
-3
lines changed

CHANGELOG.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# django-webpack-loader changelog
2+
3+
For more general information, view the [readme](README.md).
4+
5+
Releases are added to the
6+
[github release page](https://github.com/ezhome/django-webpack-loader/releases).
7+
8+
## [0.5.0] -- 2017-05-20
9+
10+
- Added ability to access the webpack asset path information from application
11+
- Fixed potential crash when formatting errors
12+
- Added django 1.11 to test suite
13+
14+
## [0.4.0] -- 2016-10-26
15+
16+
- Added ability to compile webpack to gzip bundles
17+
- Added poll interval option (time to wait between polling the stats file)
18+
- Added timeout (maximum wait-time before throwing an Exception)
19+
- Added django 1.10 to test suite
20+
21+
## [0.3.3] -- 2016-07-24
22+
23+
- Added Makefile for easier development
24+
- Added ability timeout when waiting for webpack to compile a bundle
25+
26+
## [0.3.2] -- 2016-07-24
27+
28+
- Added ability to add attrs to render_bundle tag
29+
30+
## [0.3.1] -- 2016-07-24
31+
32+
- documented webpack_static tag
33+
34+
## [0.3.0] -- 2015-02-21
35+
36+
- breaking 💥: new CACHE setting which when set to true makes the loader cache the contents of the stats files in memory. If set to True, server will restart every time the stats file contents change or it'll keep serving old, cached URLs. CACHE defaults to not DEBUG by default.
37+
- Fixed Exception
38+
- Added django 1.9 to test suite
39+
40+
## [0.2.4] -- 2015-12-23
41+
42+
- Fix unicode errors
43+
44+
## [0.2.3] -- 2015-12-03
45+
46+
- mark safe template tags
47+
48+
## [0.2.2] -- 2015-09-21
49+
50+
- fix webpack exceptions
51+
52+
## [0.2.1] -- 2015-12-03
53+
54+
- add custom exception for WebpackLoaderBadStatsError
55+
56+
## [0.2.0] -- 2015-09-10
57+
58+
- breaking 💥: revised django settings configuration syntax
59+
- webpack loader can now consume the output of multiple stats files in the same project
60+
- add ``get_files`` template tag
61+
62+
## [0.1.2] -- 2015-05-25
63+
64+
- first documented release

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,13 @@ Use webpack to generate your static bundles without django's staticfiles or opaq
1414

1515
Django webpack loader consumes the output generated by [webpack-bundle-tracker](https://github.com/owais/webpack-bundle-tracker) and lets you use the generated bundles in django.
1616

17+
A [changelog](CHANGELOG.md) is also available.
18+
1719
## Maintainers
1820
In order to overcome the lack of support for Markdown on PyPi, building this package can use [pandoc](http://pandoc.org/installing.html) along with [pypandoc](https://pypi.python.org/pypi/pypandoc) to convert the README.md into a Restructured Text format compatible with PyPI. This requires installing `pandoc` for your operating system (installation instructions on the pandoc site), and `pypandoc` which will be installed if you:
1921

2022
pip install -r requirements-dev.txt
21-
23+
2224
before uploading to PyPI.
2325

2426
If pandoc or pypandoc fails, the README.md file will be uploaded as it was before this enhancement.
@@ -168,7 +170,7 @@ and your webpack config is located at `/home/src/webpack.config.js`, then the va
168170
169171
#### TIMEOUT
170172
171-
`TIMEOUT` is the number of seconds webpack_loader should wait for webpack to finish compiling before raising an exception. `0`, `None` or leaving the value out of settings disables timeouts.
173+
`TIMEOUT` is the number of seconds webpack_loader should wait for webpack to finish compiling before raising an exception. `0`, `None` or leaving the value out of settings disables timeouts.
172174
173175
<br>
174176
@@ -310,7 +312,7 @@ the function in the `webpack_loader.utils` module.
310312
['<script type="text/javascript" src="/static/bundles/main.js" ></script>',
311313
'<link type="text/css" href="/static/bundles/styles.css" rel="stylesheet" />']
312314
```
313-
315+
314316
## How to use in Production
315317
316318
**It is up to you**. There are a few ways to handle this. I like to have slightly separate configs for production and local. I tell git to ignore my local stats + bundle file but track the ones for production. Before pushing out newer version to production, I generate a new bundle using production config and commit the new stats file and bundle. I store the stats file and bundles in a directory that is added to the `STATICFILES_DIR`. This gives me integration with collectstatic for free. The generated bundles are automatically collected to the target directory and synched to S3.

0 commit comments

Comments
 (0)