MikroORM is difficult to find using NPM search

I’ve been introduced to this project by a friend of mine and I was wondering why I haven’t heard of this project earlier - after all I’ve been looking for TypeORM replacement for quite some time and it looks like an amazing alternative.

My other friend have noticed that when you search for “orm” in NPM registry (either via text query or keyword query), MikroORM is nowhere to be found on first few pages, even though quite a few projects with way lower weekly downloads count are there. On the fifth page, a helper library @mikro-resources/fixtures is visible, but no main package in sight.

I believe that this situation hurts project discoverability a lot. Are you aware of this issue? Maybe something can be done about it.

[B4nan]

Quick update, managed to pass thru the first level support, issue is now escalated to higher level, hopefully they will help.

Also they confirmed that npm is using the data from npms.io, it can be also found in their docs:

You can use the npm search bar to find packages to use in your projects. npm search uses npms and the npms analyzer; for more information on both, see https://npms.io/about.

https://docs.npmjs.com/searching-for-and-choosing-packages-to-download

[B4nan]

Still no update from their end, but we might get around this in v4 anyway, as v4 will be monorepo with multiple packages, so hopefully those will be analyzed correctly.