django-webpack-pages
Use webpack with your multi-page, multi-lingual django webapp.
This project is based on django-webpack-loader which handles the connection to webpack. Consider using webpack-critical-pages as well if you are interested in speedups.
Put the following in your settings file:
WEBPACK_PAGES = {
"CRITICAL_CSS_ENABLED": True,
"ROOT_PAGE_DIR": osp.join(BASE_DIR, "pages"),
"STATICFILE_BUNDLES_BASE": "bundles/{locale}/", # should end in /
}
STATICFILES_FINDERS = (
"webpack_pages.pageassetfinder.PageAssetFinder",
# ... and more of your choosing:
"django.contrib.staticfiles.finders.FileSystemFinder",
"django.contrib.staticfiles.finders.AppDirectoriesFinder",
)
# configure the loaded page directories and add the WebpackExtension
TEMPLATES = [
{
"BACKEND": "django_jinja.backend.Jinja2",
"DIRS": [osp.join(BASE_DIR, "templates"), osp.join(BASE_DIR, "pages")]
+ [osp.join(BASE_DIR, app, "pages") for app in GRAZBALL_APPS]
+ [osp.join(BASE_DIR, app, "components") for app in GRAZBALL_APPS],
"APP_DIRS": True,
"OPTIONS": {
# ...
"extensions": [
# ...
"webpack_pages.jinja2ext.WebpackExtension",
],
}
}
]
Using webpack_loader.contrib.pages you can register entrypoints for corresponding pages in templates.
At the top of your individual page, do:
{% extends "layout.jinja" %}
{% do register_entrypoint("myapp/dashboard") %}
In the layout's (base template's) head, place the following:
<!DOCTYPE html>
{% do register_entrypoint("main") %}
<html lang="{{ LANGUAGE_CODE }}">
<head>
...
{{ render_css() }}
</head>
<body>
...
{{ render_js() }}
</body>
This will load the registered entrypoints in order (main, then myapp/dashboard) and automatically inject
the webpack-generated css and js. It also supports critical css injection upon first request visits.
Metadata
Release files for django-webpack-pages 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_webpack_pages-0.2.0.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_webpack_pages-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.1 kB
Release files / django_webpack_pages-0.2.0.tar.gz
| Download URL | django_webpack_pages-0.2.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d126f7d5ff368e31375bc55e6bd5c860d2556fbe61df3e66f6a91fdf8ce66f88
|
|
BLAKE2b-256 checksum How to use checksums |
ccf612cf4ef2ed8df0c41875c5612eedb5f981b24f2487d6e42e9cd705974533
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.13.3 Linux/6.14.0-36-generic
|
Release files / django_webpack_pages-0.2.0-py3-none-any.whl
| Download URL | django_webpack_pages-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55b20fd19ac7914c1a5b2873a3bd294151f124ee66f7dd55d71b0996f4ad6740
|
|
BLAKE2b-256 checksum How to use checksums |
d2edef3d84e2c9ee01a0b88dfe2b1624ba2d3e40fa04c88a4c2fcd3d0d6bbb36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.13.3 Linux/6.14.0-36-generic
|
Security for django-webpack-pages 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.