When we read package.json-files of our extensions we also register new configurations. The profile shows that this triggers event to which various part of our core react. That doesn't make sense because a built-in, core component like the welcome screen should be influenced by a setting from extension foo. This needs

• a fine-grained configuration change event that allows consumer to check what settings have changed
• adoption in the listeners