Fabrizio Ferrai

"Json errors" is unfortunately not a simple problem to solve. We parse the Yaml through Argonaut, [which returns](https://github.com/purescript/spago/blob/14dc0e20038596300f06a39cfcd76c6a89f8b6b1/core/src/Yaml.purs#L58) us a [JsonDecodeError](https://pursuit.purescript.org/packages/purescript-codec-argonaut/10.0.0/docs/Data.Codec.Argonaut#t:JsonDecodeError) - right now we are using [the default renderer](https://pursuit.purescript.org/packages/purescript-codec-argonaut/10.0.0/docs/Data.Codec.Argonaut#v:printJsonDecodeError)...

I moved this issue into Spago, as this is part of the Halogen app that we add on top of the generated docs. Sources is [here](https://github.com/purescript/spago/tree/master/docs-search/client-halogen) and PRs are most...

I don't have an opinion on the proposed change as of now, I think I'd need to see it visualised

IIRC previously it would actually group by package? I think having it always grouped by package would be the most useful - sometimes I look for the package, sometimes I...

This is very close to what the previous Spago/docs-search did. I think the "group by package" feature broke in the migration, because it was more useful then - this picture...

> Are we likely to have local copies of readmes? We are. This is not yet a thing (not sure if we even have an issue for this), but we...

We're not using the latest execa version - @JordanMartinez do you think that "just" upgrading to latest might fix this?

`spago registry search`, as the name suggests, searches for a package in the Registry. Existence of a package in the registry does not guarantee inclusion in the package set. `spago...

I think something that could help with this would be to enrich the results of `spago registry search` with a "latest package set" field

That makes sense, but I still don't get why it behaves differently when run directly with Node vs running it through Spago - it can't just be readline, it sounds...