After looking into this again, you say in the release notes that :
And, respectfully, I think that for addon developers, this is a downgrade from the previous system. While I understand that this allows for more flexibility, and the easier addition of assets to the menu, it also removes useful functionality from the python API.
Currently, there is no easy way for my addon to work in 3.4, as I cannot find out what nodes are in what categories programmatically. The only option now is to hard code all the node items, which makes it far harder to write and maintain, as it will break with every new blender update (as well as removing the notion of backwards compatibility).
I could also attempt to parse the geo nodes menu definition file, but that’s a bad idea for obvious reasons.
I have no idea if it would work, but would it not be possible to patch this new system to interface with the old NodeItems system? Or potentially create a new system that would better fit it?
I know that that would be more work, but I believe that it’s worth it to avoid removing useful functionality from the API.
Thank you for your time anyway, you do an amazing job and it’s great to see so much time being put into improving Blender