This happens because nodejs is the only plugin in your job configuration page that calls GlobalConfigFiles.getConfigs(Class<? extends Descriptor>) to populate the combobox filtering by configuration kind.
There are other plugin the invoke config-file-provider API in the job configuration page
- the config-file-provider itself, where it populate a similar combobox BUT with all kinds of configuration. It calls a different API GlobalConfigFiles.getConfigs() where descriptor
is not invoked
- maven plugin where you can choose "Maven Settings" configuration file BUT has a totally different way to provide them
To discover other extension point of config-file-provider please try to go on "Manage Jenkins" -> "Managed files" -> "Add a new Config"
Follow default kind:
- Global Maven settings.xml
- Maven settings.xml
- Json file
- Maven toolchains.xml
- Simple XML file
- Groovy file
- Custom file
- Ivy configuration
All others entries are extension point (mine is "Npm config file").
Other good tentative is delete one by one defined configuration file and at the same time reload job configuration page. When the page works the latest deleted configuration has the problem.