askvortsov I don't think that using
conflict is correct here. It will prevent installing both these extensions at the same time, while you really need to prevent enabling these extensions at the same time. It will mess up with setups like in FreeFlarum, where bunch of extensions is installed and user can pick which he wants to use. With
conflict you can't provide both these extensions.
Conflicts should probably be handled at Flarum level, when extension is enabled - you may provide better info what is the problem (output from Composer is pretty cryptic, especially for non-technical users) and prevent problems like this:
franzliedke/flarum-open-links-in-new-tab to the composer.json conflict
That could make it worse than before. Now if you you have
franzliedke/flarum-open-links-in-new-tab installed, Composer will just silently install older (
v1.6.1) release, which has known bugs and also does not work with