spago publish command

[f-f]

We should have a spago publish command, that publishes the docs for the current package to Pursuit (as pulp publish does)

[justinwoo]

Doesn't work because Pursuit requires a whole lot of bower crap, and you can't actually develop libraries this way unless you intend for them to only work with package sets

[justinwoo]

One day we won't need Bower to do library development, but that day isn't here yet

[f-f]

Would Pursuit need to be changed to require less Bower stuff or can we shim it decently?
I'm not familiar with the details, so if you have links/tribal-knowledge please dump it here

[justinwoo]

It's such a giant ball of details I think you'd need to get people in #purescript to give you some spec and also inspect mostly Pursuit, but also Pulp.

[justinwoo]

This is kind of out of scope since we'd need a package manager that actually works with version ranges afaict. But I wrote up some general information that's useful about how to work against Pursuit publishing, since sometimes the bower listing just stack overflows or OOMs or something: https://github.com/justinwoo/test-pulp-publish

[f-f]

I agree that this is not going to be directly in our scope, since it's a lot about Pursuit itself. However, since Bower itself is deprecated, IMHO we should untangle the dependency on it (as an ecosystem) ASAP. So it's worth to look into this and eventually make Pursuit easier to deal with, so that this can then be implemented decently on our end of things

PS: thanks for writing that down, good stuff 👏

[justinwoo]

"Deprecated"

[f-f]

Update on the plan for this after reading the above summary by Justin and the source of purs publish: we could generate the manifest file in bower format, and give it to purs, after
grabbing some version information for every package naively from the package set (as Pursuit needs to point to some specific version in the docs)

[f-f]

Closing this in favor of #89