What I Wanted to Do
I expect to see the most recent version/last published date for deepdash package in the search result.
What Happened Instead
I see old v3.1.3 published a month ago instead of v4.2.5 published a few days ago.
just do a search for “deepdash”:
You will see the main CJS package with outdated info and ESM version “deepdash-es” with correct version and publish date.
I suspect this issue is related to the fact of existing of multiple package.json files in the GitHub repo.
Sources of the library are splitted as ES modules and stored in the es/ directory, there is also es/package.json file to publish sources as is under deepdash-es name.
And the main package deepdash is published with CJS files built by rollup.
So, possibly, the search engine sees GitHub repo was indexed once for deepdash-es package and skip second re-indexing for deepdash package.
It’s npmjs/npms bug
I posted an issue:
but there is still no reaction. So I hope to trigger some attention here. Or maybe somebody will recommend a workaround.