Updated to support webpack-build@1.0.0. Note that webpack-build needs to be invoked with
the -s flag to boot the server. For example, node_modules/.bin/webpack-build -s.
API
- Added the
populate_manifest_filefunction
Settings
- Added the
HMRsetting, which toggles support for hot module replacement - Added the
USE_MANIFEST,MANIFEST,MANIFEST_PATH, andMANIFEST_SETTINGSsettings, which provide support for offline manifests - Added the
POLLsetting, which toggles the behaviour of webpack's file watcher in non-OSX environments - Added the
BUILD_URLsetting, which denotes a url to an endpoint exposing webpack-build - Added the
CONFIG_DIRSsetting, which enables lookups for relative paths to config files - Added the
CONTEXTsetting, which denotes the default context sent to config functions - Added the
CACHEandCACHE_DIRsettings, which control webpack-build's persistent file cache
Dependencies
- Added a dependency on the webpack-build JS package
API
webpack.compiler.webpacknow accepts the signature(config_file, [context], [settings], [manifest], [compiler])
Settings
OUTPUT_DIRnow defaults to 'webpack_assets'BUNDLE_URLis nowSTATIC_URLBUNDLE_ROOTis nowSTATIC_ROOTWATCH_SOURCE_FILESis nowWATCHWATCH_DELAYis nowAGGREGATE_TIMEOUT
API
- Removed the undocumented config file writer
Settings
- Removed the BUNDLE_DIR and CONFIG_DIR settings
- Removed the WATCH_CONFIG_FILES setting. In practice it proved to introduced memory leaks leading to inevitable segmentation faults
Dependencies
- Removed the js-host dependency.
- Removed the python-js-host dependency.
- Removed the webpack-wrapper dependency.
- Python 3 fixes.
- Added a config file writer.
- The directory specified by the BUNDLE_DIR setting is now nested in another directory specified by OUTPUT_DIR.
- Added a setting CONFIG_DIR, which is nested in OUTPUT_DIR.
- Fixed an import error when configuring webpack from django.
- Renamed the project from django-webpack to python-webpack.
- The django dependency is no longer required, comparable functionality is still preserved if you choose to use django.
- The project is now imported as
webpack, formerly it wasdjango_webpack. - Ported the JS dependency from django-node to js-host.
- The django staticfiles helpers are now located in
webpack.django_integration.
- Bug fixes and improvements to the JS service
- The API is now oriented around config files, rather than programmatically generating config.
- Updated django-node dependency to latest
- Updated django-node dependency to latest
- Updated django-node dependency to latest
- Python 3 fixes
django_webpack.webpack.bundleis now available atdjango_webpack.bundle.django_webpack.models.WebpackBundleis now available atdjango_webpack.WebpackBundle.
- Improving the test harness and updating django-node to the latest.
- The default value for
WebpackBundle.devtoolis now defined by a setting, DJANGO_WEBPACK['DEVTOOL'] - The default value for the
DJANGO_WEBPACK['CACHE']setting is now toggled byDJANGO_WEBPACK['DEBUG'], rather thandjango.conf.settings.DEBUG.
- API changes:
django_webpack.models.WebpackBundle.outputis nowdjango_webpack.models.WebpackBundle.path_to_outputdjango_webpack.models.WebpackBundle.get_outputis nowdjango_webpack.models.WebpackBundle.get_path_to_output
- Added an optional in-memory cache, triggered by the setting
DJANGO_REACT['CACHE'].
- django_webpack.models.WebpackBundle can now be invoked directly.
WebpackBundle(entry='path/to/file.js')
- Added a test suite.
django_webpack.webpack.bundlenow offers trivial programmatic access to webpack.- Moved the Webpack configuration settings from settings.py to
django_webpack.models.WebpackBundle.
- Initial release