Fabrizio Ferrai

I cannot find the relevant issue in the purescript repo unfortunately. I can only say that so far the recommended workflow is `spago install package-name` and `spago build --deps-only`. I'm...

We are generally fine with breaking changes, that's not really the issue here. The reason why I have doubts about this is that we'd change the general meaning of the...

Maybe we should separate `spago install` (renaming it to `spago fetch`) from `spago install package-name`. In this way it would make sense that `fetch` does a different thing than `install`,...

> What are the real use cases for using `fetch` vs installing and building the package? People often want separate commands to just download the packages (which requires network) vs...

I was wondering - is this work necessary at all now that we have [the backend optimizer](https://github.com/aristanetworks/purescript-backend-optimizer)?

@rhendric I agree with you - my point here is that the new backend has shuffled the landscape quite a bit: it shows not only that it's possible to aggressively...

@rainbyte yes, having `output` in the config file would be nice! Ideally you'd want all the flags to be configurable also through the config file, but since we've been iterating...

Yes! We should definitely add this option to the `WorkspaceConfig`, and as a global flag on the command line

The main roadblock for this feature is that one could also pass `--output` inside `--purs-args` - we should prevent that and instead handle it only on the Spago side, to...

@Profpatsch yeah sorry for that, the way we treat the config file is fairly magick for a series of historical reasons. I hope to solve all of this by switching...