We should probably build the webpack-generated resources as part of our deployment workflow (see deploy.yml).
This would ensure that the web assets are always in sync with the sources in our webpack subdirectory. (E.g. we could just merge dependabot PRs like #355 without having to manually run webpack afterwards.)
This is probably as simple as setting up Node, then adding -f webpack to the lektor build command.
If/when we do this, we should perhaps remove the built resources from version control (since they will be overwritten on every deployment anyway).
We should probably build the webpack-generated resources as part of our deployment workflow (see deploy.yml).
This would ensure that the web assets are always in sync with the sources in our webpack subdirectory. (E.g. we could just merge dependabot PRs like #355 without having to manually run webpack afterwards.)
This is probably as simple as setting up Node, then adding
-f webpackto thelektor buildcommand.If/when we do this, we should perhaps remove the built resources from version control (since they will be overwritten on every deployment anyway).