Arnout Engelen

> `Embed in Shell-Scripts` could also go into the `Develop` category perhaps? yeah that makes sense to me > Regarding `nix-env` and `nix profile`: Do you recommend only documenting `nix...

I think that looks pretty cool! It could probably use some more instructions and links to relevant documentation, but I like the general direction.

I generally like the idea. I wonder if we should hook into searching all of https://github.com/nix-community/nix-index somehow

While I'm not opposed to having playwright tests, I wouldn't want you to spend a bunch of time writing them and then being disappointed when nobody shows up to implement...

> [@raboof](https://github.com/raboof) to be honest, my hope was that you implement the feature, and I help by providing some end to end tests. :) Honestly I'd _like_ to, but there's...

I don't have any suggestions offhand. Perhaps you could at each derivations' dependencies, and for each package only list the libraries that are not part of any dependency package? That...

> This approach still finds me many packages that re-export libraries, something the data in this project does not know about. We may be able to remove some duplicates with...

> Not sure I like to find a place to host the API. It seems much more logical to enhance the ingress of data into ElasticSearch and then later enhance...

I have no idea if that's expected/useful or a bug, but I guess we could just exclude all python-*-env from the search result?

> From my end, I think this is probably good enough to get a first stab at adding those library references to the package definitions in the open search database....