I am getting a reoccurring question about my package’s config. The specific config takes an array of paths to ignore for a search and has some defaults (e.g. node_modules) already defined.
When the user changes the array it overrides the defaults, which forces the user to copy the existing config to be able to extend the list, which is not very nice. On the other hand, if I extend the config behind the scenes, the user will be unable to remove the defaults that he/she doesn’t want.
What could a reasonable solution to this be? Could anyone point me to a package that solves a similar problem?