While moving from ancient hardware to more modern hardware, somehow Visual Studio Code had updated itself to a version that didn’t support the underlying operating system any more. Bummer!
Normally I would get the list of extensions through this command (which is listed in many places, like in my blog post How can you export the Visual Studio Code extension list? (via: Stack Overflow), but also for instance answered in the below question by [WaybackSave/Archive] Benny Ng):
code --list-extensions
That obviously would not work, but thanks to [Wayback/Archive] How can you export the Visual Studio Code extension list? – Stack Overflow (thanks [Wayback/Archive] Andrew and [Wayback/Archive] MarkP) I now could do this:
ls -alh ~/.vscode/extensions
(That directory obviously is also in various forms of official documentation like in the the Your Extensions Folder section of [Wayback/Archive] Publishing Extensions | Visual Studio Code Extension API.
A comment to the above question pointed me to an interesting way to automate extension installs on various machines: pack the installed extension list into its own .vsix file:
The Wiert Corner - irregular stream of stuff 