2270ff425a
* Add dev tools for live-reloading the web stack while running Anki * Handle CDP connection errors more graciously * Include sass in web stack watchers * Refactor monitored folder and event definition * Switch to more specific build target Thanks to @hikaru-y * Add PyChromeDevTools to dev requirements * Update rebuild-web for ninja * Satisfy mypy * Remove ts-watch Superseded by web-watch (the version here was also still based around bazel) * Simplify calls to other build tools Given that `./ninja qt/aqt` has to be run from the project root anyways, it doesn't make sense to use calls relative to `rebuild-web` in an ill-guided effort to lower dependencies on hard-coded paths. * Remove remaining script-relative tool path |
||
---|---|---|
.. | ||
licenses.json | ||
licenses.sh | ||
mkempty.py | ||
README.md | ||
requirements.anki.in | ||
requirements.aqt.in | ||
requirements.base.in | ||
requirements.base.txt | ||
requirements.bundle.in | ||
requirements.bundle.txt | ||
requirements.dev.in | ||
requirements.dev.txt | ||
requirements.qt5_14.in | ||
requirements.qt5_14.txt | ||
requirements.qt5_15.in | ||
requirements.qt5_15.txt | ||
requirements.qt6_3.in | ||
requirements.qt6_3.txt | ||
requirements.qt6_4.in | ||
requirements.qt6_4.txt | ||
requirements.win.in | ||
requirements.win.txt | ||
update_python_deps.sh | ||
update_win_deps.bat | ||
write_wheel.py |
- To achieve reproducible builds we use pip-tools to lock packages to a particular version - see update_python_deps.sh
- write_wheel.py is used to generate our wheels.