In short, upgrading Visual Studio to vsn 2019 16.8.5 or later (and maybe earlier) breaks BundlerMinifier vsn 3.2.499 (the latest).
This issue covers the problem in more detail but no need to read it to help me out.
To be specific, the context menu on the bundleconfig.json no longer appears, but that's just the easiest symptom to spot.
The big problem behind the missing menu is that new or altered JavaScript isn't being bundled or minified, changes to bundleconfig.json aren't being detected, .js files not being rebundled on build and can't be told to manually etc.
What I'm trying to find out is whether anyone out there is using BunderMinifier with this or later versions of Visual Studio and still gets the context menu.
A few people have reported the same problem, not just me, so I'm wondering if either (1) hardly anyone uses it these days, (2) there is a problem with just a few users/projects, of which I am one, or ... (3) people aren't updating VS.... not likely, or (4) ... has to be 1 or 2 I guess, but it'd help in finding a solution if I knew which - it's presumably and hopefully (2) as it means I can almost certainly fix it locally, though I've tried everything I can think of during the last few weeks.
Re-installs of the NuGet package, Visual Studio itself or a complete Windows install don't fix it (I was doing one anyway) - I've also tried removing the json files and re-adding them, adding them with different names, all sorts.
Any help appreciated, even just a single 'Still works fine here' would be helpful (ideally with VS and BundlerMinifer versions)