Improve NPM searchability

[LoganDark]

Right now, when searching for "react tree" on NPM, aspen-tree-model and aspen-decorations don't show up until page 5. However, react-aspen is still nowhere to be found until page 28!

This must have been the reason why I couldn't find it weeks and weeks ago when I searched heavily for a tree view package and could not find one for the life of me - aspen doesn't show up for tens of pages! Clearly this is not a great situation to be in, especially since it seems like an incredibly useful and performant library.

I was only able to find out about aspen after begging for a tree view library in the Reactiflux Discord server. Perhaps making it easier to search up will allow others to discover it more easily as well?

[zikaari]

Thanks for actively opening an issue around this. I'm aware of this problem but I'm not aware of a solution.

I'm just not very knowledgeable when it comes to SEO. I do have set up the obvious keywords one might imagine, including react and tree, and more. I even have the word React and trees in the package.json's description field. I even mention the word "tree" multiple times in the readme, I even cross-reference react-virtualized-tree in there. NPM's "page rank" is just playing games here.

I would truly appreciate some help with making this package more visible. I worked really hard on making this library, and it's sad if when people need it, they can't even find it, when it is out in the open.

[LoganDark]

I would truly appreciate some help with making this package more visible. I worked really hard on making this library, and it's sad if when people need it, they can't even find it, when it is out in the open.

I feel you. It is very sad knowing that I probably would've never found this library if not for that blessed soul in the Reactiflux server. I'm also at a loss trying to figure out how your search ranking could be this bad, especially because of the great quality of the library.