Fabrizio Ferrai

Ah indeed - the output of the compiler is going through PSA, so I think we should be able to patch it there? (cc @JordanMartinez)

> I don't see it working out with mixed versions (differences per property field). We wouldn't mix versions per field, we'd either accept the current config or the new one,...

Automatically upgrading the config format is a good idea, but it might take quite a few lines - we have a "yaml printer", but editing the configuration is not just...

Yes I think that once we recognise the old config and auto-upgrade it then we don't need to do much else here - we'll want to add a few tests...

I had a look at #1168 and had a chat with Jordan about the patch - we are both not very happy with the typeclass-based solution - it's very generic...

Superseded by #1202

Upgrade to optparse 6 is blocked on #1129 That example parser is not very close to the one we use in Spago, we have [different prefs](https://github.com/purescript/spago/blob/b450892d69aa3013861fde6c73299d2c17aba3dc/bin/src/Main.purs#L491), then there's a separate...

How is it not clear? It says "path".

I am not sure we customise that: https://github.com/purescript/spago/blob/6d8e02f379a550c1b142a5ae577c4f406bf649f4/bin/src/Flags.purs#L67-L73

Before using `spago bundle` it's a good idea to ask oneself where this bundle will be put. The help text has a flag to override this location. We should note...