The npm configuration:
- Includes linting of javascript with eslint
The webpack setup here:
- Bundles javascript and css, using hashing to support server-side
caching, with support from Flask-Webpack and
manifest-revision-webpack-plugin
- Uses babel to transpile ES6 javascript
- Includes a development server with hot-replacing of javascript and
css code
* Update flake8-docstrings from 0.2.5 to 1.0.2
* Update werkzeug from 0.11.4 to 0.11.11
* Update sqlalchemy from 1.0.12 to 1.1.3
* Update flake8-quotes from 0.2.4 to 0.8.1
* Update webtest from 2.0.20 to 2.0.23
* Update flask-wtf from 0.12 to 0.13.1
* Update flake8-blind-except from 0.1.0 to 0.1.1
* Update isort from 4.2.2 to 4.2.5
* Update flake8-isort from 1.2 to 2.0.1
* Update pep8-naming from 0.3.3 to 0.4.1
* Update factory-boy from 2.6.1 to 2.7.0
* Update pytest from 2.9.0 to 3.0.3
* Update psycopg2 from 2.6.1 to 2.6.2
* Update flask-login from 0.3.2 to 0.4.0
* Update flake8 from 2.5.4 to 3.0.4
- Update Flask to 0.11 (with built-in Click integration)
- Remove manage.py
- Add autoapp.py per Flask doc's new recommendations
for using Click with an app factory
- Define cookiecutter-flask's commands in cli.py
- Register shell context and shell commands as part
of factory-based app creation
- Update README instructions with examples for running
commands in new Click style
Flask-Migrate was recently patched to version 1.3.1 because [alembic versions can now include parts that are not integers](https://github.com/miguelgrinberg/Flask-Migrate/pull/51).
Requiring Flask-Migrate 1.3.0 installs a version of alembic that results in the following error message on startup:
`ValueError: invalid literal for int() with base 10: 'post2'`
Changing the requirements to install Flask-Migrate 1.3.1 fixes this problem.