Currently there is no way to detect changes to files in the browse paths outside the workspace folder.

One way to solve this would be to add file system watchers to browse paths outside the workspace folder, but that can be expensive. An alternative would be to have an API for customConfigurationProviders to force a rescan.

In our scenario, changes to paths outside the workspace folder often times happen due to a build, which if done via our extension, can trigger the rescan.