Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

organization namespaced packages do not appear to be sorted #18

Closed
andykais opened this issue Apr 5, 2020 · 2 comments
Closed

organization namespaced packages do not appear to be sorted #18

andykais opened this issue Apr 5, 2020 · 2 comments

Comments

@andykais
Copy link

andykais commented Apr 5, 2020

regular package names appear to be sorted by dependency count but organization namespaces appear to be out of order. E.g. these are the first 10 that appear in the list

 andrew  ~  all-the-package-names | grep '^@' | head -10
@yuliy/supermodule
@kwiatkk1/native-dns
@eknkc/s3cp
@inversion-of-control/modular-electron-example-vendors
@beisen/skeleton
@johnhooks/dollar
@insin/babel-plugin-react-transform
@tonypythoneer/status
@xyezir/string-replace-loader
@caseywebb/hypernasa
@jialu/nodeapp
@react-material/button
@react-material/fab
@jwaterfaucett/animation_frame
@typed/is-promise

e.g. @types/is-promise has 1 dependent while @yuliy/supermodule has 0.

@zeke
Copy link
Member

zeke commented May 3, 2020

Hey @andykais. Sorry for the late reply.

Unfortunately, the sorting by dependency count is based on very outdated counts, which are not automatically updated. The counts come from https://github.com/nice-registry/dependent-counts which has not been updated in several years 😬

If you're interested in contributing to resolve this, I'd be happy to work together on it.

@Richienb Richienb mentioned this issue Jul 13, 2020
@zarianec
Copy link
Collaborator

zarianec commented Feb 7, 2022

As @zeke mentioned before, the sorting logic depends on outdated package. We don't have any estimates on when we could fix it and it's not our priority at the moment.

Because of that, we decided to drop this feature in a new versions of all-the-package-names.

See #26

@zarianec zarianec closed this as completed Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants