Config split ignore dependencies I'm using the config_split module to split configuration to an installation profile, that I use in multiple Drupal sites.

I have 2 sites using the same installation profile, both using the same config split settings.

Here's a list of configuration that I have split to the profile.


The content type (article)
Taxonomy vocabularies
Media types
Media library views and settings


I have 4 content types on one of the sites, but I only want to split the article content type.

The problem is that some fields from the other content types are automatically split because they depend on either media or taxonomy.

This is the node configuration that I'm splitting:


  
  core.base_field_override.node.article.*
  core.entity_form_display.node.article.*
  core.entity_view_display.node.article.*
  core.entity_view_mode.node.article.*
  field.field.node.article.*
  field.storage.node.article*
  


All fields from the article content type are all named article_FIELD_NAME.

How can I avoid that config split also splits depending configuration?
I solved that problem using Features for Drupal 8 as suggested by @leymannx.

I have exported media, taxonomy and the article content type to one feature that I can now use across multiple sites.

The cool thing is that configuration still lives in the config_sync directory, so other content types that depend on media and taxonomy don't need to be exported to features as well.