Should we make exported dependencies from extensions easily disabled

[dlmr]

In the coming version of Roc it will be possible for extensions to explicitly define dependencies that they want to expose/export to the project.

Currently there is two ways to disable this behaviour if needed. One that work on a per import basis and the other that is more permanent, however a little complex requiring the use of the new init function inside the projects roc.config.js.

The question is if will be a common scenario to disable exported dependencies and if so if we then should provide a simpler API for permanently disable an exported dependency.

This could for example be done through an object inside roc.config.js that might look something like this:

{
  react: false,
  lodash: false 
}

Will revisit this when we have more data to go on.