entity browsers should have config dependency on config that references them

I think that we should do it the other way around. Components that are using entity browsers should declare them as dependencies. Fields widgets that this module ships with are a good candidate it seems.

Something like this?

Manually tested and it appears to work as expected, after this modification when deleting an entity browser being referenced, the confirmation screen is shown, indicating that the display settings on the node form will be updated.

Have a doubt though on the ->getSetting() call. Is it possible that this returns a non-empty but invalid value? (like an empty array or something like this) In this case it would be better to wrap this inside an !empty() check.

Looks OK to me. Just a nitpik:

+++ b/src/Plugin/Field/FieldWidget/FileBrowserWidget.php
@@ -493,4 +493,19 @@ class FileBrowserWidget extends EntityReferenceBrowserWidget {
+  /**
+   * {@inheritdoc}
+   */
+  public function calculateDependencies() {
+    $dependencies = parent::calculateDependencies();

Since FileBrowserWidget extends EntityReferenceBrowserWidget we don't need to re-implement same logic again.

Have a doubt though on the ->getSetting() call. Is it possible that this returns a non-empty but invalid value? (like an empty array or something like this) In this case it would be better to wrap this inside an !empty() check.

You could try to load the entity browser to be sure. If this value is wrong there will be much more problems than just wrong dependencies though.

True, sorry!

Committed. Thanks!