This is part of a series describing how I am changing my entire stack for developing web applications. My choices are driven by security and simplicity.
- Part I: Intro and Rationale
- Part II: Linux
- Part III: Python/Django
- Part IV: HTMX
- Part V: VSCode and Copilot
- Part VI: Bulma
- Part VII: Sqlite
- Part VIII: uv
This part will be a catch-all for VSCode extensions and other tools. Some are new to me, some came over from other projects.
- coverage.py – I use this on Page-o-Mat, which is also in Python.
- Coverage Gutters – this shows coverage right in VSCode. It works with anything that produces standard coverage files, so it works well with coverage.py. I wrote about how I use that here and in my book.
- mutmut – This is something I have been playing around with in Page-o-Mat because of my interest in mutation testing. I contributed a feature a few months ago, which I’ll cover later this month. I’ll be using it more seriously now.
- flake8 and black – for linting and auto-formatting. This is more necessary as I use AI since its style adherence isn’t perfect.
I still haven’t figured out what I will do for JS testing. I used jest before, but it doesn’t meet my criteria of low-dependencies. Might have to start with this gist for TestMan.
I also need to replace my code complexity extension (it was for JS/TS). I might see how long I can last without it because the main replacements don’t have enough usage to consider installing (VSCode extensions are another hacking vector, like supply chain attacks).